I’m working on jupyter/gui and have run into a (big?) issue. It seems that the API is designed so that you always have to get sliver (i.e. node/link/component) info from the slice manager (i.e. from the fabric service). However, if I have already opened a topology I should be able to get the info from the local copy without contacting any fabric services. This is really important with a gui that may have lots of update/display operations before a slice is submitted to fabric. We can’t have every one of those be a remote service call.
Is there a reason why most all of the methods in ExperimentTopology are private?
It is possible to get some of the info but you need to do it like this:
myNode.set_property(pname=“name”, pval=“newname”)
myNode.get_property(pname=“name”)
You can use the following:
myNode.name = “newname2"
print(myNode.name)
but these do NOT set the names that end up in the serialized topology.
Maybe I’m missing something. How am I supposed to access these vars in an un-submitted topology?
Per Paul:
I’m working on jupyter/gui and have run into a (big?) issue. It seems that the API is designed so that you always have to get sliver (i.e. node/link/component) info from the slice manager (i.e. from the fabric service). However, if I have already opened a topology I should be able to get the info from the local copy without contacting any fabric services. This is really important with a gui that may have lots of update/display operations before a slice is submitted to fabric. We can’t have every one of those be a remote service call. Is there a reason why most all of the methods in ExperimentTopology are private? It is possible to get some of the info but you need to do it like this: myNode.set_property(pname=“name”, pval=“newname”) myNode.get_property(pname=“name”) You can use the following: myNode.name = “newname2" print(myNode.name) but these do NOT set the names that end up in the serialized topology. Maybe I’m missing something. How am I supposed to access these vars in an un-submitted topology?