Hi Russell, I've attached a draft diagram for Compute. Could you please review, or send it to someone who can? (I didn't worry about the look of the thing, branding will come after.) thank you, Summer
(In reply to Summer Long from comment #3) > Hi Russell, I've attached a draft diagram for Compute. Could you please > review, or send it to someone who can? (I didn't worry about the look of the > thing, branding will come after.) thank you, Summer I've added Nikola to get one more review, but here are my comments: 1) Remove the arrow between nova-api and nova-cert. 2) This might get messy in the diagram, but Console/VNC should not be connected to RabbitMQ. It should be connected to nova-novncproxy. Also, novncproxy should be connected directly to the libvirtd driver. 3) nova-api talks directly to the block storage and networking services, as well. 4) The object storage service does not use rabbitmq. There is *very* little direct integration with object storage, anyway. I think there might be something in EC2 support. For an architecture diagram, I would remove it. 5) The block storage service *does* use rabbitmq, but not in relation to its integration with compute. I would leave that connection off of the diagram. Thanks!
(In reply to Russell Bryant from comment #4) > (In reply to Summer Long from comment #3) > > Hi Russell, I've attached a draft diagram for Compute. Could you please > > review, or send it to someone who can? (I didn't worry about the look of the > > thing, branding will come after.) thank you, Summer > > I've added Nikola to get one more review, but here are my comments: > > 1) Remove the arrow between nova-api and nova-cert. > > 2) This might get messy in the diagram, but Console/VNC should not be > connected to RabbitMQ. It should be connected to nova-novncproxy. Also, > novncproxy should be connected directly to the libvirtd driver. > This is correct but novncproxy also does connect to RabbitMQ to validate tokens, however this is probably not relevant from the diagram standpoint, although you could leave it for completeness. Also it should not be connected to the database. As for 5), actually both API and compute hosts interact with block storage, but through it's HTTP API, so you can do 2 direct lines, or just connect it with a different type of arrow to the diagram as a whole. This is actually true for the networking service as well - so it might be easier if you did block storarge in the same way as networking. I think that covers it - everything else looks solid.
Created attachment 1009329 [details] Compute Architecture rev.2 Compute Architecture rev.2
Russell, Nikola, here's an update. Could you please check? thanks, Summer
The only thing I would change on the latest attachment is that I would connect user directly to openstack-nova-novncproxy service and drop completely the Console/VNC box (maybe add VNC caption to the arrow but not too important). Otherwise it's good to go IMHO
Sent diagram to Jess for look at new brand/style.
Moving to Sprint 5 tracker.