You get create, destroy and get (a very small amount of) information about a server using the eschedule command. It needs to know where and have access to the etcd and placement services. This is fine for the testing that's happened thus far, but limiting.
Another option would be to have a very simple WSGI app over the same calls that eschedule does. That is, a wsgi app that would call methods in ecomp/schedule.py.
As with #6 this opens up concepts of users and auth, but in this case it could probably be boot off.
Simple API could go like this:
POST /?resources=<resources>&image=<url>
<<< instance id
GET /{instance id}
<<< ip
DELETE /{instance id}
This maps directly to the existing commands.
Hard to say if this is worth doing. Really only if other people come along.
You get create, destroy and get (a very small amount of) information about a server using the
eschedulecommand. It needs to know where and have access to the etcd and placement services. This is fine for the testing that's happened thus far, but limiting.Another option would be to have a very simple WSGI app over the same calls that
escheduledoes. That is, a wsgi app that would call methods inecomp/schedule.py.As with #6 this opens up concepts of users and auth, but in this case it could probably be boot off.
Simple API could go like this:
This maps directly to the existing commands.
Hard to say if this is worth doing. Really only if other people come along.