renci-nrig / ahab Goto Github PK

fix Sudo permissions and storage dependencies

Add bin directory with pyscripts to master

Setting the slice term should work. Flukes cannot extend AHAB-created slices. This may also be a problem with Flukes being too sensitive.

@dcvan24 @clarisca

So users don't complain about missing dependencies.

Long term issue for keeping track of use cases that test ahab/exogeni

• ComputeNodes. Including testing of all attributes (setting and getting)
• Networks. Including testing of all attributes (setting and getting)
• StitchPorts. Including testing of all attributes (setting and getting)
• StorageNodes. Including testing of all attributes (setting and getting)
• Timing of refresh. A quick refresh after a commit will get occasionally get an incomplete manifest
• Intra. vs. Interdomain connections often have very different issues
• Requests vs. modifies often have very different issues

AutoIP reassigns in use IP in case of modifySlice.

Issue exists because the order in which interfaces are processed in Network::autoIP function are processed is not deterministic.

Solution is to traverse all the interfaces which have IP addresses allocated should mark ip as used in subnet. Once subnet is populated, allocate IPs for new interfaces.

I attempted to set bandwidth for BroadcastNetwork instances by calling its setBandwidth() method and it didn't take effect. The bandwidth was still the default 10Mbps as shown in the created request.

Python scripts that exercise the controller XMLRPC APIs are written in 2.6 and don't work past that. Needs an update.

Support to create debian package for xoStitch Utility

It should be "PSC (Pittsburgh, PA, USA) XO Rack", not PSC (Pittsburgh, TX, USA) XO Rack.

Changes required to support Dynamo

• AutoIP does not work for modify
• Support for Storage
• Support for LinkConnection

Loading a manifest RDF for a multipoint/interdomain slice doesn't seem to create the underlying SliceGraph correctly when one does Slice s = Slice.loadManifest(manifest). There are no interfaces (i.e. s.getInterfaces().size() = 0), and hence one can't obtain the data plane IPs. It works fine in the intra-domain case.

The create and modify methods on ISliceTransportAPIv1 have the following signatures:

public abstract String modifySlice(String sliceId, String modReq) throws TransportException, ContextTransportException;

public abstract String createSlice(String sliceId, String resReq, SliceAccessContext<? extends AccessToken> sliceCtx) throws TransportException, ContextTransportException;

I think the createSlice method does not nee the sliceCtx parameter. The proxy should already know the context b/c it is required to create a proxy. It would be simpler and more consistent if none of the api calls required the context. Otherwise libndl need to keep track of both the proxy and the context for each slice.

The ComputeNode instance returns no ManifestNode instance, which contains ComputeNode state information as observed in NDLlib. The getState() method of the Network instance returns null.

Remove unused gson dependency in ahab to avoid conflicts with jclouds

s.getInterfaces() returns a list of interfaces in the slice, but each interface appears twice

@paul-ruth @congwang09 Somewhere between Paul and Cong we need to produce some basic documentation for AHAB. It would be fine to create an ExoBlog (and may be preferable) and then link to it from the README file in this repo.

In relation to #6, create a Maven Archetype to help generate sample applications using Ahab.