1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 241 through 255 (of 402 total)
  • Author
    Posts
  • in reply to: No output using iperf for network monitoring #6489
    Komal Thareja
    Participant

      Attaching the notebook again.

      in reply to: No output using iperf for network monitoring #6486
      Komal Thareja
      Participant

        Hi Robin,

        Acheme is right. Management Network only supports SSH via bastion node and basic ICMP packets. We do not recommend conducting your experiments with Management Network.

        Please consider modifying your experiment where you are also requesting a local network (L2Bridge or FabNetv4/FabNetv6) since all your VMs are on the same site. Setup your Segment routing using the data plane network instead of the management network. There are several examples available under Networking  in the start_here.ipynb

        Also, I am enclosing a sample notebook, which requests the VMs and connects them with local L2 Network(IPv6). You can use this as a base and setup Segment Routing on the Data Plane interfaces. Please let us know if you have questions or run into any issues.

        NOTE: Please rename the notebook from .jpg to .ipynb as the forum doesn’t allow attaching files with .ipynb extension.

        Thanks,

        Komal

        in reply to: Spawn failed: Timeout launching JupyterHub server #6484
        Komal Thareja
        Participant

          Worked with Vaiden to clean up JH container and also shared the complete back up with him.

          He also wasn’t able to view his slices created via account linked to older email. Applied a patch on CF to address that. He is able to list the slices now.

          Thanks,

          Komal

          in reply to: Error in creating a cluster with multiple nodes #6473
          Komal Thareja
          Participant

            Hi Manas,

            I noticed some of your slivers are in Closed state with the error: Last ticket update: Redeem/Ticket timeout

            I applied a patch to address this last night. Could you please delete this slice and try again? We are monitoring the system to see if the patch addresses the issue. As of now, we do not have a consistent way to reproduce this problem. Please keep us informed if you run into this again.

            Thanks,

            Komal

            in reply to: Error in creating a cluster with multiple nodes #6465
            Komal Thareja
            Participant

              Hi Manas,

               

              I sent you updated notebook with the email. Some more improvements from the last version. Bit easier network configuration. I was able to create a slice on UCSD with this. Could you please try this and let me know how it goes?

              Thanks and Regards,

              Komal

              in reply to: Can’t access Jupyter Hub #6459
              Komal Thareja
              Participant

                Yes, another user had a similar issue where they created a new email alias but were registered with FABRIC with different email. Changing your preferred email to point to what you were using before should help resolve this.

                Thanks,

                Komal

                in reply to: 403 : Forbidden Access to JupyterHub #6456
                Komal Thareja
                Participant

                  Good morning Polycarp,

                  This something you would have to look at your account settings. I won’t be able to help much there. In the meanwhile, could you please try accessing JHUB again?

                  Thanks,

                  Komal

                  in reply to: Error in creating a cluster with multiple nodes #6450
                  Komal Thareja
                  Participant

                    Hi Manas,

                    I tried your notebook and was able to figure out the issue. You are specifically passing in the flavor names in your notebook. We do not recommend that, instead we request the user to pass in the specific cores, ram and disk needed.

                    In release 1.6, the underlying flavors were re-provisioned to allow for more disk/ram/core combinations which resulted in your slivers being closed due to incorrect configuration.

                    Making following changes in your notebook to explicitly pass the cores, ram and disk resolves this issue.

                    I have also created a BUG on Control Framework software to return more informative error in such cases for easier debugging. Thank you for reporting this and helping us make the testbed better.


                    node=slice.add_node(name=node_names,
                    site=site,
                    #instance_type=instance_master,
                    cores=8,
                    ram=12,
                    disk=500,
                    image=image)

                    NOTE: I have emailed you the updated notebook.

                    P.S: I am still looking at Redeem Timeout issues if you run into that, will share an update regarding those tomorrow.

                    Thanks,

                    Komal

                    in reply to: 403 : Forbidden Access to JupyterHub #6446
                    Komal Thareja
                    Participant

                      I suspect that multiple email aliases were configured recently for your account. JHUB queries user roles based on your email. In this case, your email address is being passed as polycarpnalela@missouri.edu to JHUB.

                      LDAP has your information stored with polycarpnalela@mail.missouri.edu and hence LDAP query returns no information for your account resulting in access denied as indicated in the error below.

                      Is it possible for you to change your email configuration to allow polycarpnalela@mail.missouri.edu as the primary email address?

                       

                      [W 2024-01-29 00:02:22.712 JupyterHub fabricauthenticator:37] FABRIC user polycarpnalela@missouri.edu is not in CO:COU:Jupyterhub:members:active

                       

                      Thanks,

                      Komal

                      in reply to: 403 : Forbidden Access to JupyterHub #6442
                      Komal Thareja
                      Participant

                        Are you trying to login to JH using the email address: polycarpnalela@mail.missouri.edu

                        Which Identity provider are you using when you login via CILogon?

                        Also, could you please share the snapshot of what you see on the following link after logging on to Portal?

                        Please also share the cookie contents as well.

                        https://portal.fabric-testbed.net/check-cookie

                        Also, try opening JH on an incognito browser window and see if that helps.

                        Thanks,

                        Komal

                        in reply to: 403 : Forbidden Access to JupyterHub #6439
                        Komal Thareja
                        Participant

                          Hello Polycarp,

                           

                          Could you please check on the portal if you are a member of a project? This error typically occurs if you are not a member of a project.

                          Thanks,

                          Komal

                          in reply to: Can’t access Jupyter Hub #6438
                          Komal Thareja
                          Participant

                            @Vaiden – This generally happens if you are not a member of a project. Could you please check on the portal if you are a member of a project?

                            Thanks,

                            Komal

                            in reply to: Error in creating a cluster with multiple nodes #6437
                            Komal Thareja
                            Participant

                              Hi Manas,

                              Thank you for sharing your observations. I see one of the VMs failed to provision on UCSD and resulted in rest of the slivers being closed by orchestrator. Could you please try creating your slice again or share your notebook? I don’t have enough information to debug this further and would like to reproduce in our environment.

                              Appreciate your help with this!

                              Thanks,

                              Komal

                              in reply to: Maintenance on Network AM – 01/26/2024 (9:00am-10:00am EST) #6427
                              Komal Thareja
                              Participant

                                Maintenance is complete!

                                in reply to: error when setting up a slice #6424
                                Komal Thareja
                                Participant

                                  Could you please check /tmp/fablib/fablib.log for any errors? Also could you please check if you are able to SSH to the VMs in your slice from command line?

                                  Also, please share your notebook if possible to help us recreate this in our environment.

                                  Thanks,

                                  Komal

                                Viewing 15 posts - 241 through 255 (of 402 total)
                                FABRIC invites nominations for four awards recognizing innovative uses of FABRIC resources—Best Published Paper, Best FABRIC Matrix, Best FABRIC Experiment, and Best Classroom Use of FABRIC — submissions due by **Monday, February 24 at 11:59 PM ET**, and winners announced at KNIT10. [>>>Submit Form](https://docs.google.com/forms/d/e/1FAIpQLSeTp3i2iDhB7bHgN8ryMxZci8ya87yjeQd7_JMZImUodNinVA/viewform)

                                KNIT10 Call for Demos Now Open! Submit your demo by **February 24**. [>>>Submit Demo](https://docs.google.com/forms/d/e/1FAIpQLScRIWqHliNP3DFWBCnalYN_fBXJXVM0PpP9YWWJdSebC95TvA/viewform)
                                FABRIC invites nominations for four awards recognizing innovative uses of FABRIC resources—Best Published Paper, Best FABRIC Matrix, Best FABRIC Experiment, and Best Classroom Use of FABRIC — submissions due by **Monday, February 24 at 11:59 PM ET**, and winners announced at KNIT10. [>>>Submit Form](https://docs.google.com/forms/d/e/1FAIpQLSeTp3i2iDhB7bHgN8ryMxZci8ya87yjeQd7_JMZImUodNinVA/viewform)

                                KNIT10 Call for Demos Now Open! Submit your demo by **February 24**. [>>>Submit Demo](https://docs.google.com/forms/d/e/1FAIpQLScRIWqHliNP3DFWBCnalYN_fBXJXVM0PpP9YWWJdSebC95TvA/viewform)