Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-21 Thread George Shuklin
Directions: nova->switch port, switch port -> glance, glance->switch port (to swift). I assume traffic from switch to swift outside installation. Glance-api receive and send same amount of traffic. It sounds like a minor issue until you starts to count CPU IRQ time of network card (doubled co

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-21 Thread Michael Dorman
This is great info, George. Could you explain the 3x snapshot transport under the traditional Glance setup, please? I understand that you have compute —> glance, and glance —> swift. But what’s the third transfer? Thanks! Mike On 1/21/15, 10:36 AM, "George Shuklin" wrote: >Ok, news so

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-21 Thread George Shuklin
Ok, news so far: It works like a magic. Nova have option [glance] host=127.0.0.1 And I do not need to cheat with endpoint resolving (my initial plan was to resolve glance endpoint to 127.0.0.1 with /etc/hosts magic). Normal glance-api reply to external clients requests (image-create/download/

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-18 Thread matt
+1 On Sun, Jan 18, 2015 at 10:05 PM, Jay Pipes wrote: > On 01/15/2015 05:20 PM, George Shuklin wrote: > >> Hello everyone. >> >> One more thing in the light of small openstack. >> >> I really dislike tripple network load caused by current glance snapshot >> operations. When compute do snapshot,

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-18 Thread Jay Pipes
On 01/15/2015 05:20 PM, George Shuklin wrote: Hello everyone. One more thing in the light of small openstack. I really dislike tripple network load caused by current glance snapshot operations. When compute do snapshot, it playing with files locally, than it sends them to glance-api, and (if gl

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-15 Thread George Shuklin
We do not using centralized storages (all instances running with local drives). And I just can't express my happiness about this. Every time monitoring send me '** PROBLEM ALERT bla-bla-bla', I know it not a big deal. Just one server. I do not want to turn gray prematurely. Just light glance o

Re: [Openstack-operators] Small openstack (part 2), distributed glance

2015-01-15 Thread Abel Lopez
That specific bottleneck can be solved by running glance on ceph, and running ephemeral instances also on ceph. Snapshots are a quick backend operation then. But you've made your installation on a house of cards. On Thursday, January 15, 2015, George Shuklin wrote: > Hello everyone. > > One more

[Openstack-operators] Small openstack (part 2), distributed glance

2015-01-15 Thread George Shuklin
Hello everyone. One more thing in the light of small openstack. I really dislike tripple network load caused by current glance snapshot operations. When compute do snapshot, it playing with files locally, than it sends them to glance-api, and (if glance API is linked to swift), glance sends t