[Bruce Hartpence]

Sure – what is the best way to share the notebook with you?

[Bruce Hartpence]

Quick update – tried WASH but it failed during provisioning for all nodes. Tried NEWY and I’m up and running.

[Bruce Hartpence]

Thanks – I’ll give that a try and get used to IPv6 man interfaces.

[Bruce Hartpence]

Quick update – tried MASS an got the same problem but looking a little deeper at the error I see this:

No more IP addresses available on network 0073521c-8e08-4a7d-9abf-b9ec59b0d749

 

[Bruce Hartpence]

Yes – it looks like it doesn’t affect slice operation. That’s what authentication errors are for 🙂

[Bruce Hartpence]

Thanks Komal – that did the trick.

[Bruce Hartpence]

OK thanks. I moved the affected nodes to MAX.

[Bruce Hartpence]

I just learned a new word and now I am wondering about the etymology of “cruft” 🙂

[Bruce Hartpence]

I don’t know if this helps or not but I have nodes on both L3 and L2 networks and the sample notebooks have been very helpful. The potential “gotcha” is that networks have to be defined, interfaces on those internal links must be given an IP address and be brought up before they can PING.

IP assignment can be done manually or by the addresses available on that network.

[Bruce Hartpence]

OK, I’ll rerun stuff and check for the above. Thanks all – I’ll let you know how it goes.

[Bruce Hartpence]

Not sure if it’s related but I am getting other errors too. When running

#L3 fabnet auto
from ipaddress import ip_address, IPv4Address, IPv6Address, IPv4Network, IPv6Network
import ipaddress

from fabrictestbed_extensions.fablib.fablib import FablibManager as fablib_manager
fablib = fablib_manager()

I get the following error:

SliceManagerException: b'{\n “errors”: [\n {\n “details”: “error: Core API error occurred status_code: 404 message: b\'{\\\\n \\”errors\\”: [\\\\n {\\\\n \\”details\\”: \\”No match for Project with uuid = \\\\\’b55cc265-97af-4597-8c2f-c38b0618d3e\\\\\’\\”,\\\\n \\”message\\”: \\”Not Found\\”\\\\n }\\\\n ],\\\\n \\”size\\”: 1,\\\\n \\”status\\”: 404,\\\\n \\”type\\”: \\”error\\”\\\\n}\’, refresh_token: NB2HI4DTHIXS6Y3JNRXWO33OFZXXEZZPN5QXK5DIGIXTINJXGAYGEMLCG42WGZTFMU4DEODGMY2GCYRXGAZTEOBSGQ4GINB7OR4XAZJ5OJSWM4TFONUFI33LMVXCM5DTHUYTMOJSGAZTONZZG42DCNRGOZSXE43JN5XD25RSFYYCM3DJMZSXI2LNMU6TQNRUGAYDAMBQ”,\n “message”: “Internal Server Error”\n }\n ],\n “size”: 1,\n “status”: 500,\n “type”: “error”\n}’

[Bruce Hartpence]

Hi Mert – I’m not sure I follow you. I have the bastion and slice keys but I do not think I have access to or control of the VM key you mentioned.

This is a very recent problem as I have been playing with the VMs for a couple of weeks although I am not ruling out an error between the keyboard and the chair.

[Bruce Hartpence]

Found it  – it is under the “start_here” –> “Customizing nodes”

Code snip:

slice_name = ‘MySlice1′

#Create Slice
slice = fablib.new_slice(slice_name)

# Add node
node = slice.add_node(name=’Node1′,
site=’MAX’,
host=’max-w1.fabric-testbed.net’,
cores=4,
ram=16,
disk=100,
image=’default_ubuntu_20′)

#Submit Slice Request
slice.submit()

[Bruce Hartpence]

Thanks Ilya – that looks like it worked. My only question would be about the example from which the host command was derived.

[Bruce Hartpence]

Whelp, I’m going to disappoint you as I am using the portal for everything except SSH connectivity. I’ll work on switching to notebooks for configuration.

Your comment on IPv6 management makes total sense and seems consistent with all of the experiences I’ve had so far but perhaps getting IPv6 as the default should be examined as it might add to the configuration requirements.

PSC – ahh, OK

and I’ll play with the FABNetv4 services. Though I must say, L2Bridge makes more sense to my brain. For right now I will push the “I believe” button on FABNetv4 but I would love to chat about how this works under the hood some time.

[Author]

Posts