Hello ladies, This is my first email to the women of openstack mailing list and I hope I'll find some support here. My name is Sara and i'm an engineering student In France. Right Now i'm doing my final intership before graduation and I'm working on Openstack. I need to scale some VMs based on CPU, RAM and Network workloads combined. I started with basic things. Now my VMs can scale up and down based on CPU. BUT when I try to connect them to a load balancer nothing works. I really need to make this first step work.So for those of you who already played with autoscaling, can you please provide me with clues , examples, tutos I can use to do a first demo for my team?! Looking forward to hearing from you, Sara P.S: find attached my templates -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20150529/c444789d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: environment1.yaml Type: application/octet-stream Size: 76 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20150529/c444789d/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: scale_up_down_lb.yaml Type: application/octet-stream Size: 3489 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20150529/c444789d/attachment-0001.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: scale_up_down_NoLb.yaml Type: application/octet-stream Size: 1412 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20150529/c444789d/attachment-0002.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: single_instance.yaml Type: application/octet-stream Size: 526 bytes Desc: not available URL: <http://lists.openstack.org/pipermail/women-of-openstack/attachments/20150529/c444789d/attachment-0003.obj>