[Openstack-operators] Operating Swift

e for choosing server hardware for storage and proxy node. I've read that proxy node is network and CPU intensive but as I don't have traffic, I don't know which specification I should choose (for example 8 CPU, 32GB ram, etc). Your experience is appreciated. Regards, --

Re: [Openstack-operators] Operating Swift

suggested RAM is 1G per 1TB. I will have enough ram. Hopefully, it will work smoothly. Thanks again for the links. Regards, -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler

[Openstack-operators] Migrating to Different Availability Zone and Different Storage

downtime (live migration)? Regards, Eren -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc Description: OpenPGP digital signature

[Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

cope link fe80::f816:33ff:fee8:fd4b/64 dev qg-690ab8d9-81 scope link } virtual_routes { 0.0.0.0/0 via 192.168.88.1 dev qg-690ab8d9-81 } END: keepalived.conf on NODE-2 -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Univ

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

On 26-05-2015 11:15, Eren Türkay wrote: > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: ip address associated > with > VRID not present in received packet : 169.254.0.1 > May 26 10:54:15 neutron-ha-2 Keepalived_vrrp[20144]: one or more VIP > associated > with VRID mism

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

darchive repository? Regards, Eren -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc Description: OpenPGP digital s

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

response! I will try with the exact same code on both neutron servers. I wasn't aware that minor version could affect this behavior. I will probably go for ubuntu 14.04 with cloudarchive repositories for neutron servers (version 2.3.8). Regards, -- Eren Türkay, System Administrator https://s

Re: [Openstack-operators] Neutron HA With VRRP (2 Master Nodes, Bogus VRRP packet)

internal IP addresses will change, causing the VM operator to change the configuration of as well. Any ideas? Regards, Eren -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107

Re: [Openstack-operators] Small Operators

eet you and happy hacking, Eren -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc Description: OpenPGP

Re: [Openstack-operators] Gentoo image availability

t which I specified. So, it would be really great if you can support hot-plugging for ethernet devices and DHCP. I find them very useful and I believe many people would expect this feature from Gentoo image. Regards, -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885

Re: [Openstack-operators] SSH to a VM instance created

vaclient Please make sure that your networking components are working properly and you have metadata proxy running. Otherwise, the VM will not be able to get your ssh key and it will boot with empty ssh key. The usernames for the cloud images can vary. For ubuntu, you need to login as "ubuntu&q

Re: [Openstack-operators] Could not get IP to instance through neutron

On 17-06-2015 02:08, pra devOPS wrote: > Stderr: 'ovs-ofctl: br-int is not a bridge or a socket\n' I think this error is clear. br-int seems to be created in a wrong way. How did you create this interface? -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885

[Openstack-operators] Which Puppet Modules To Use?

the big tent seem to be developed as well. Regards, [0] https://wiki.openstack.org/wiki/Puppet -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc

Re: [Openstack-operators] Which Puppet Modules To Use?

for those modules are hosted in github repository: https://github.com/openstack?utf8=%E2%9C%93&query=puppet > Regards, > > Richard Raseley Regards, -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark

[Openstack-operators] Juno and Kilo Interoperability

, our Horizon and other clients will be Juno, but they will talk to secondary site which is Kilo. Inferring from the release notes, Kilo API looks backward compatible with Juno, so I'm a little optimistic about it but still I'm not sure. Any help is appreciated, Eren -- Eren Türk

Re: [Openstack-operators] Juno and Kilo Interoperability

On 26-08-2015 17:17, Jonathan Proulx wrote: > We recently upgraded from Juno to Kilo and many of our clients > (including Horizon) are still Juno with no problems. Great news. That's our use case. We will have Juno clients and Kilo API endpoints. Thank you for your help. --

Re: [Openstack-operators] Juno and Kilo Interoperability

is Kilo, and Juno keystone/horizon is shared). I think it will just work. When upgrading the Juno site, I will start with nova and will take your responses into account. That's when I will have Juno+Kilo in one site. Regards, -- Eren Türkay, System Administrator https://skyatlas.com/ | +9

[Openstack-operators] Kilo neutron-ns-metadata-proxy Problem

inside the namespace can be found here: http://paste.ubuntu.com/12237691/ Regards, -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc Descriptio

Re: [Openstack-operators] [neutron] Kilo neutron-ns-metadata-proxy Problem

On 31-08-2015 14:56, Eren Türkay wrote: > Hello, Hello agiain, > I installed Kilo neutron. I can create networks, namespaces are created and > neutron-ns-metadata-proxy is running. However, VM's cannot get SSH keys. I've > isolated the problem down the network namespace and

Re: [Openstack-operators] [neutron] Kilo neutron-ns-metadata-proxy Problem

On 07-09-2015 11:52, Ihar Hrachyshka wrote: > See metadata_access_mark option in etc/l3_agent.ini Hello, This option is set 0x1 by default. The debug log prints: metadata_access_mark = 0x1 Should I change this value to another one? -- Eren Türkay, System Administrator ht

Re: [Openstack-operators] [neutron] Kilo neutron-ns-metadata-proxy Problem

On 07-09-2015 10:29, Eren Türkay wrote: > I am still stuck at this problem. Has anyone experienced it? I would be really > happy if someone can give a tip regarding to the issue. Hello all, Sorry for the inconvenience. I misinterpreted the actual error. Instances could reach to the namespa

[Openstack-operators] Mirantis Fuel Multi-Region

/api endpoints for each region. Is this always the case with Fuel? Is there anyone who has installed multi-region Openstack with Mirantis Fuel? Thanks for your time, -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu

Re: [Openstack-operators] Mirantis Fuel Multi-Region

tp://lists.openstack.org/pipermail/openstack-dev/2015-October/076298.html -- Eren Türkay, System Administrator https://skyatlas.com/ | +90 850 885 0357 Yildiz Teknik Universitesi Davutpasa Kampusu Teknopark Bolgesi, D2 Blok No:107 Esenler, Istanbul Pk.34220 signature.asc Desc