| *** andrey-mp has quit IRC | 01:23 | |
| *** ansiwen has quit IRC | 01:23 | |
| *** andrey-mp has joined #openstack-ec2api | 01:24 | |
| *** ansiwen has joined #openstack-ec2api | 01:24 | |
| *** andrey-mp has quit IRC | 06:08 | |
| *** andrey-mp has joined #openstack-ec2api | 09:49 | |
| *** andrey-mp has quit IRC | 10:02 | |
| *** andrey-mp has joined #openstack-ec2api | 13:04 | |
| ansiwen | andrey-mp: hi! Happy new year! EmillienM from tripleo/puppet projects said he would like to see separate services for separate containers in the ec2api and ec2api-metadata case. from an update perspective, does it make sense to run these services in separate containers? does it make sense to run them in separate containers in any other aspect? | 15:16 |
|---|---|---|
| *** lane_maxwell has joined #openstack-ec2api | 16:45 | |
| *** lane_maxwell has quit IRC | 17:50 | |
| andrey-mp | ansiwen: hi! | 18:07 |
| andrey-mp | happy new year! | 18:07 |
| andrey-mp | I think that here is the same as for nova-api and nova-metadata | 18:08 |
| andrey-mp | from an update perspective there is no difference. | 18:20 |
| andrey-mp | both services are just a proxy to other openstack services. both services use one DB. | 18:21 |
| andrey-mp | so these services can be run in one container and in separate containers... | 18:23 |
| andrey-mp | I can't choose one variant - both will work well | 18:25 |
| *** lane_maxwell has joined #openstack-ec2api | 18:28 | |
| *** lane_maxwell has quit IRC | 19:29 | |
| *** lane_maxwell has joined #openstack-ec2api | 19:30 | |
| *** lane_maxwell has quit IRC | 21:25 | |
| *** lane_maxwell has joined #openstack-ec2api | 21:47 | |
| *** lane_maxwell has quit IRC | 22:28 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!