Forum Replies Created
-
Posts
-
I think you are asking about your experiment running a service that is accessible over the Internet.
This will be possible. Longer term we will enable L3 services on your experiment’s dataplane that can be connected to the Internet. This service is not ready now. For now, you can expose a service on the Internet using the management plane. We are working on a way for you to tunnel that service through our bastion host. We have the tunnel working but need to create some documentation that shows you how to use it.
Paul
Fengping,
We are looking into this. It does look like your slice is up. We need to investigate more to see what is wrong with the VMs.
I’ll add more info when I know it.
Paul
Fu Shen,
There isn’t really a way to save the state of a slice. We recommend scripting the configuration of your experiments so that you can easily bring the experiment up/down. Some configuration can take a long to to build. In these cases, you might want to create containers to package your software so that the can easily be deployed on the VMs.
I am working on some examples using DockerHub to deploy software. One example that is not quite done yet but could be useful is a slice that deploys a P4 software switch using DockerHub.
An initial version of the notebook can be found here: https://github.com/fabric-testbed/jupyter-examples/blob/pruth-utils/fabric_examples/beta_functionality/fabric_p4_bmv2/fabric_p4_simple_router.ipynb
Note that this example uses some utility functions to copy scripts into the VMs then runs them. The scripts run “docker run …” and other configuration. Building the software in this docker container takes a couple of hours but installing the pre-built container take about a minute. This streamlines the creation of the experiment and makes it very easy to share the experiment with other users.
Paul
Fu Shen,
There isn’t really a way to save the state of a slice. We recommend scripting the configuration of your experiments so that you can easily bring the experiment up/down. Some configuration can take a long to to build. In these cases, you might want to create containers to package your software so that the can easily be deployed on the VMs.
I am working on some examples using DockerHub to deploy software. One example that is not quite done yet but could be useful is a slice that deploys a P4 software switch using DockerHub.
An initial version of the notebook can be found here: https://github.com/fabric-testbed/jupyter-examples/blob/pruth-utils/fabric_examples/beta_functionality/fabric_p4_bmv2/fabric_p4_simple_router.ipynb
Note that this example uses some utility functions to copy scripts into the VMs then runs them. The scripts run “docker run …” and other configuration. Building the software in this docker container takes a couple of hours but installing the pre-built container take about a minute. This streamlines the creation of the experiment and makes it very easy to share the experiment with other users.
Paul
I just approved Jason. His account was still pending but should work how. I need to check on Muhammad’s account.
Good question. For now, the only images available are “default_ubuntu_20” and “default_centos_8”. We plan to enable custom images at a later date. Let us know if you have a specific experiment that needs a different OS flavor.
Generally, custom images are useful if you have specific Linux flavor, kernel, or device driver requirements. We recommend packaging software in Docker containers. Starting an experiment can use a baseVM image followed by pulling a Docker container from a service such as Docker Hub. Stay tuned for a software P4 switch example that I will release soon. It loads the experimental software suing Docker Hub.
Can you try again but make sure that all cookies related to FABRIC and CIlogon are deleted first? There may be some weird state related to the previous attempts. I know you said he tried with a different browser but I just want to make sure he never tried with the new browser before.
I agree this would be ideal. The issue is that the forums/learn site is WordPress under the covers. We have looked into single sign on across our custom portal and WordPress, but there are other priories at the moment.
Thanks for the feed back. Streamlining login is something we will be working toward.
You definitely can add multiple connectX-6 card. Given our very limited dev capacity, it may be that there are no nodes left that have 2 connectX-6’s in the same host.
What is the error you see in the sliver status for that failed VM?
(see this example to get sliver status: https://github.com/fabric-testbed/jupyter-examples/blob/master/fabric_examples/basic_examples/get_slivers.ipynb)
Yes, that is all correct. The only additional thing to think about is if you add VLAN tags to the interfaces. If there are VLAN tags you need create the virtual interfaces inside the VM.
Also, if you are using a L2P2P you must use a VLAN tag. If you are not seeing traffic this could be why.
Paul
Does the slivers method do it?
Like in this notebook: https://github.com/fabric-testbed/jupyter-examples/blob/master/fabric_examples/basic_examples/get_slivers.ipynb
`
