1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 391 through 405 (of 411 total)
  • Author
    Posts
  • in reply to: fabric-cli does not produce valid JSON #3246
    Komal Thareja
    Participant

      Thank you Timothy and Sajith for your contributions! Appreciate it! I have approved the PR and merged to the master branch. Will create a new release and push to Jupyter Hub.

      in reply to: Slices stuck in “Closing” or “Configuring” state #3174
      Komal Thareja
      Participant

        Slices in Closing state do not have any resources allocated to them. They can be ignored. They stay in the Closing state as the confirmation for the delete response from the various Sites is not received (potentially because of the Kafka timeouts). These slices do not prevent the creation of new slices with the same name. We are working to improve the Kafka timeouts and would work to address the issue of Closing slices in the upcoming release.

        Slices in Configuring state would prevent the creation of a new slice with the same name. I checked all the slices listed above and they are all in Closing state.

        Thank you so much for sharing your observations and help us make the testbed better.
        Please do share the slice id of the slices in Configuring state if you do run into them again.

        in reply to: Two problem I am having so far for logging into FABRIC VMs #3136
        Komal Thareja
        Participant

          No worries, I was able to reproduce this issue by creating a slice from the GUI. We will work on resolving this, thank you for helping us identify this problem and make the testbed better. Appreciate your feedback.

          in reply to: Two problem I am having so far for logging into FABRIC VMs #3134
          Komal Thareja
          Participant

            We are working to investigate this behavior and would appreciate if you please share the slice id of the slice created from the portal? This would help us gather the required information quickly.

            Appreciate your help!

            Thanks

            in reply to: renew slice did not fully work #3078
            Komal Thareja
            Participant

              Also, from previous conversation, I found that the slice was renewed on Sep 8. Could you please let us know when did you loose SSH connectivity?

              in reply to: renew slice did not fully work #3076
              Komal Thareja
              Participant

                Hello Gregory,

                I can see both the VMs for your slice are ACTIVE. However, I am unable to SSH into them. I will seek help from operations team and keep you posted.

                
                Reservation ID: da5faa94-1c50-41b7-abf5-47578a82b87b Slice ID: 4cb0a209-ca5e-4479-b0b7-e192fe257964
                Resource Type: VM Notices: Reservation da5faa94-1c50-41b7-abf5-47578a82b87b (Slice MySliceSep12B(4cb0a209-ca5e-4479-b0b7-e192fe257964) Graph Id:d854653d-cf7b-407d-ae4d-149c5113262b Owner:aroy59@asu.edu) is in state (Active,None_)
                Start: 2022-09-13 15:50:24 +0000 End: 2022-09-18 03:54:26 +0000 Requested End: 2022-09-18 03:54:26 +0000
                Units: 1 State: Active Pending State: None_
                Sliver: {'capacities': '{ core: 32 , ram: 128 G, disk: 100 G}', 'capacity_allocations': '{ core: 32 , ram: 128 G, disk: 100 G}', 'capacity_hints': '{ instance_type: fabric.c32.m128.d100}', 'image_ref': 'default_rocky_8', 'image_type': 'qcow2', 'label_allocations': '{ instance: instance-0000132a, instance_parent: tacc-w3.fabric-testbed.net}', 'management_ip': '129.114.110.85', 'name': 'CMBS4Node_tacc2', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', '8QQBZC3')", 'reservation_info': '{"error_message": "", "reservation_id": "da5faa94-1c50-41b7-abf5-47578a82b87b", "reservation_state": "Active"}', 'site': 'TACC', 'type': 'VM'}
                ('CMBS4Node_tacc2-nic2', {'capacity_allocations': '{ unit: 1 }', 'details': 'Mellanox ConnectX-6 VPI MCX653 dual port 100Gbps', 'label_allocations': '{ bdf: 0000:e2:0f.6}', 'model': 'ConnectX-6', 'name': 'CMBS4Node_tacc2-nic2', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', '8QQBZC3-slot7')", 'type': 'SharedNIC'})
                
                Reservation ID: 2571ddf7-f838-46b8-9095-ed0d36cfec55 Slice ID: 4cb0a209-ca5e-4479-b0b7-e192fe257964
                Resource Type: L2STS Notices: Reservation 2571ddf7-f838-46b8-9095-ed0d36cfec55 (Slice MySliceSep12B(4cb0a209-ca5e-4479-b0b7-e192fe257964) Graph Id:d854653d-cf7b-407d-ae4d-149c5113262b Owner:aroy59@asu.edu) is in state (Active,None_)
                Start: 2022-09-13 15:50:25 +0000 End: 2022-09-18 03:54:26 +0000 Requested End: 2022-09-18 03:54:26 +0000
                Units: 1 State: Active Pending State: None_
                Sliver: {'layer': 'L2', 'name': 'net1', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', 'node+tacc-data-sw:ip+192.168.16.3-ns')", 'reservation_info': '{"error_message": "", "reservation_id": "2571ddf7-f838-46b8-9095-ed0d36cfec55", "reservation_state": "Active"}', 'type': 'L2STS'}
                {'capacities': '{ unit: 1 }', 'label_allocations': '{ mac: 02:FA:69:DF:46:DD, vlan: 2121, local_name: HundredGigE0/0/0/5, device_name: ncsa-data-sw}', 'labels': '{ mac: 02:FA:69:DF:46:DD, vlan: 2121, local_name: HundredGigE0/0/0/5, device_name: ncsa-data-sw}', 'name': 'CMBS4Node_ncsa1-CMBS4Node_ncsa1-nic1-p1', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', 'port+ncsa-data-sw:HundredGigE0/0/0/5')", 'type': 'ServicePort'}
                {'capacities': '{ unit: 1 }', 'label_allocations': '{ mac: 06:34:B9:B2:55:E2, vlan: 2124, local_name: HundredGigE0/0/0/9, device_name: tacc-data-sw}', 'labels': '{ mac: 06:34:B9:B2:55:E2, vlan: 2124, local_name: HundredGigE0/0/0/9, device_name: tacc-data-sw}', 'name': 'CMBS4Node_tacc2-CMBS4Node_tacc2-nic2-p1', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', 'port+tacc-data-sw:HundredGigE0/0/0/9')", 'type': 'ServicePort'}
                
                Reservation ID: 430e4832-f048-4368-b8b6-51ff6a5b6932 Slice ID: 4cb0a209-ca5e-4479-b0b7-e192fe257964
                Resource Type: VM Notices: Reservation 430e4832-f048-4368-b8b6-51ff6a5b6932 (Slice MySliceSep12B(4cb0a209-ca5e-4479-b0b7-e192fe257964) Graph Id:d854653d-cf7b-407d-ae4d-149c5113262b Owner:aroy59@asu.edu) is in state (Active,None_)
                Start: 2022-09-13 15:50:24 +0000 End: 2022-09-18 03:54:26 +0000 Requested End: 2022-09-18 03:54:26 +0000
                Units: 1 State: Active Pending State: None_
                Sliver: {'capacities': '{ core: 32 , ram: 128 G, disk: 100 G}', 'capacity_allocations': '{ core: 32 , ram: 128 G, disk: 100 G}', 'capacity_hints': '{ instance_type: fabric.c32.m128.d100}', 'image_ref': 'default_rocky_8', 'image_type': 'qcow2', 'label_allocations': '{ instance: instance-0000072a, instance_parent: ncsa-w1.fabric-testbed.net}', 'management_ip': '2620:0:c80:1001:f816:3eff:feef:a24c', 'name': 'CMBS4Node_ncsa1', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', 'F1FSZB3')", 'reservation_info': '{"error_message": "", "reservation_id": "430e4832-f048-4368-b8b6-51ff6a5b6932", "reservation_state": "Active"}', 'site': 'NCSA', 'type': 'VM'}
                ('CMBS4Node_ncsa1-nic1', {'capacity_allocations': '{ unit: 1 }', 'details': 'Mellanox ConnectX-6 VPI MCX653 dual port 100Gbps', 'label_allocations': '{ bdf: 0000:a1:1f.2}', 'model': 'ConnectX-6', 'name': 'CMBS4Node_ncsa1-nic1', 'node_map': "('508c3fa3-df17-41ab-bb95-fdf71c105a61', 'F1FSZB3-slot6')", 'type': 'SharedNIC'})
                
                
                • This reply was modified 2 years, 6 months ago by Komal Thareja.
                in reply to: ‘FablibManager’ object has no attribute ‘project_id’ #3074
                Komal Thareja
                Participant

                  Hello Xusheng,

                  This error is typically observed when either FABRIC_PROJECT_ID environment variable is not set or an explicit parameter project_id is not passed when creating instance of FablibMananger.

                  Could you please verify and try again and share the snapshot of the error observed?

                  Thanks,
                  Komal

                  in reply to: issues with renew slice using 1.3 #2868
                  Komal Thareja
                  Participant

                    Thank you for let us know! We will work on fixing the example. Please use the snippet below to renew the slice.
                    Hope this helps!

                     

                    
                    import datetime
                    
                    #Set end host to now plus 1 day
                    now = datetime.now(timezone.utc)
                    end_date = now + timedelta(days=6).strftime("%Y-%m-%d %H:%M:%S %z")
                    
                    try:
                    slice = fablib.get_slice(name=slice_name)
                    
                    slice.renew(end_date)
                    except Exception as e:
                    print(f"Exception: {e}")
                    
                    in reply to: error in slice submit : `refresh_token` must not be `None` #2817
                    Komal Thareja
                    Participant

                      Could you please invoke the show_config() and share the output before invoking new slice?
                      Also, could you please verify that the token file has refresh_token and json looks like below:

                      P.S: You may already have it in correct format.

                      
                      {"id_token": "YOUR ID Token",
                      "refresh_token": "YOUR Refresh Token",
                      "created_at": "timestamp"}
                      
                      fablib.default_fablib_manager = FablibManager()
                      
                      fablib.show_config()

                      show_config would list the token file being used, please verify that it is correct.

                      Thanks,

                      Komal

                      in reply to: error in slice submit : `refresh_token` must not be `None` #2804
                      Komal Thareja
                      Participant

                        Hi Gregory,

                        Thank you for reporting this issue. Could you please share the snapshot of the stacktrace if available where this error is observed or share your notebook?

                        Also, could you please share the output of the command below?

                        cat /opt/conda/lib/python3.9/site-packages/fabrictestbed/__init__.py

                        Also, are you using the Jupyter Hub or local desktop environment?

                        If you are using the desktop environment, please consider updating the python environment using the following command:

                        pip install fabrictestbed-extensions==1.3.0

                        Thanks and Regards,

                        Komal

                        Komal Thareja
                        Participant

                          Greg, could you please delete this slice and recreate it?

                          We had some leftover layer3 connections from testing which were causing the issue. We were able to identify and clear them. It should work now. Please let us know if you still face this issue.

                          Komal Thareja
                          Participant

                            Hi Chengyi,

                            As discussed on slack, I looked at your slice: e10be783-2ef6-407e-bb9b-14a1103317a9

                            Slivers for the slice do have the updated lease time on the orchestrator. But the update could not be reflected at the Aggregates as the token used to trigger the renew had expired. I would also try to reproduce this issue on our development setup and work on providing a fix for it.

                            All the slivers report the error:

                            Reservation ID: 2b5bf824-8472-4af9-b4c0-b8137fd27f45 Slice ID: e10be783-2ef6-407e-bb9b-14a1103317a9
                            Resource Type: VM Notices: Reservation 2b5bf824-8472-4af9-b4c0-b8137fd27f45 (Slice SciStream-demo-more-accurate(e10be783-2ef6-407e-bb9b-14a1103317a9) Graph Id:0ae993ab-2775-4b15-befe-3f4e2ec3fb3d) is in state (Closed,None_) (Last ticket update: Unable to validate provided token: ValidateCode.INVALID/Signature has expired) (Ticket events: Unable to validate provided token: ValidateCode.INVALID/Signature has expired)

                            • This reply was modified 2 years, 9 months ago by Komal Thareja.
                            in reply to: Session/Slice/Project tag issues. #2109
                            Komal Thareja
                            Participant

                              Thank you for sharing the observations. fabric-cli creates FABRIC tokens for the user which are then used to authenticate/authorize with the testbed. The lifetime of FABRIC identity token is 1 hour.

                              A new token is created if the expiry time is < 30 mins from the current time. The tokens are cached in ~/.tokens.json.

                              In the above scenario, even though the project id was changed, the cached token may not have been re-requested due to the time-limit as explained above thus resulting in the Create Slice being successful.

                              We would work on addressing this in the next release. Appreciate your feedback.

                              Komal Thareja
                              Participant

                                fabric-cli currently does a json dump of the Slice object thus resulting in the escaping of the inner json objects. We would work on making this output more parseable in the next releases until then using the FABlib interface which returns the Python objects is recommended.

                                in reply to: Failed fabrictestbed install on Python 3.10 #1763
                                Komal Thareja
                                Participant

                                  Current Fabric components are based on Python 3.9. Some of the underlying dependencies we are using are not available for Python 3.10 yet so upgrade to 3.10 doesn’t work.

                                  • This reply was modified 2 years, 10 months ago by Komal Thareja.
                                Viewing 15 posts - 391 through 405 (of 411 total)