CLOUDSTACK COLLABORATION CONFERENCE 2019 - LAS VEGAS

[Paul Angus]

Hi Fellow CloudStack People.

Hopefully you have all heard that *CCCNA2019* will be happening on September 
9th-11th 2019 in *Las Vegas* in in conjunction with ApacheCon.
And the CFP closes *13th May*

If not, in summary CCC (CloudStack Collaboration Conference) is where we try to 
get together as much of the community as possible.
We have two days of talks, usually with 2 tracks, plus a day of 'hackathon' 
where people can get together in a huddle and discuss issues and or write code.
That works out to be about 32 slots of up to 45 minutes.

The presentations can be from developers, vendors, cloud operators, end users 
or basically anyone who works with CloudStack in some way and has
something they'd like to share.  This can be new features being developed or 
recently released; beginner, intermediate, or advanced presentations on
aspects of CloudStack; lessons learnt from developing or using a feature or 
maybe tips for other who are running CloudStack clouds.  It may be from a
vendor who has a CloudStack integration that will "Change your life"(tm)

Everyone is welcome to submit a presentation/workshop/panel discussion, and 
everyone is welcome to attend.  It doesn't matter if you use CloudStack,
used to use CloudStack or are thinking about using CloudStack.  There are 
always many interesting talks (and people) to hear.
CCCNA19 will be part of ApacheCon, so you will be able to mingle and attend 
other Apache Foundation Projects talks as well.

CCC is always a great social occasion on top of all  the technical content, and 
being in Las Vegas this year, that's kinda unlikely to change.

*So please, put CCC in your calendar, put in a submission  
http://us.cloudstackcollab.org/#schedule BY the 13TH  MAY and meet the family.*


SEE YOU IN LAS VEGAS!!

Paul Angus












paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Re: Cloudstack-agent gets the local IP address exception

[Andrija Panic]

That sounds great Li, glad you solved the problem.

On Tue, 23 Apr 2019 at 16:49, li jerry  wrote:

> Hi Andrija
>
>
>
>   Your method is very good. I just tested agent. lb. When management
> fails, the agent can complete switching in a very short time.
>
>
>
>
>
> 
> 发件人: Andrija Panic 
> 发送时间: Tuesday, April 23, 2019 10:22:47 PM
> 收件人: dev
> 抄送: us...@cloudstack.apache.org
> 主题: Re: Cloudstack-agent gets the local IP address exception
>
> Hi Jerry,
>
> not a good idea, if you don't mind me saying that.
>
> Are you using 4.11 release ? If so you should use the internal LB logic
> that is now part of Agent on KVM side - please check this one:
> https://www.shapeblue.com/software-based-agent-lb-for-cloudstack/
>
> Let me know if this works for you.
>
> Best,
> Andrija
>
> On Tue, 23 Apr 2019 at 14:59, li jerry  wrote:
>
> > HI Dag Sonstebo
> >
> > We deploy management and agent on the same host, with three such nodes.
> > So we need to deploy keepalived on these three nodes, elect a VIP, and
> let
> > all agents communicate with this VIP.
> >
> > 发件人: Dag Sonstebo
> > 发送时间: 2019年4月23日 17:08
> > 收件人: us...@cloudstack.apache.org;
> > dev@cloudstack.apache.org
> > 主题: Re: Cloudstack-agent gets the local IP address exception
> >
> > Li,
> >
> > Why do you run with this configuration? If this is for network resilience
> > you would run a bond/team, not keepalived.
> >
> > Regards,
> > Dag Sonstebo
> > Cloud Architect
> > ShapeBlue
> >
> >
> > On 22/04/2019, 14:37, "li jerry"  wrote:
> >
> > HI All
> >
> >
> > my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via
> > keepalived.
> >
> > After I started the cloudstack-agent, I got vip[10.226.16.10] and I
> > couldn't get the correct IP [10.226.16.11];
> >
> > Can I have any way to get the cloudstack agent to get the correct IP
> > address?
> >
> >
> >
> > Cloudstack 4.11.2
> > CentOS 7.5
> >
> >
> >
> > br2:  mtu 1500 qdisc noqueue state
> UP
> > group default qlen 1000
> > link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
> > inet 10.226.16.11/24 brd 10.226.16.255 scope global
> noprefixroute
> > br2
> >valid_lft forever preferred_lft forever
> > inet 10.226.16.10/24 scope global secondary br2
> >valid_lft forever preferred_lft forever
> > inet6 fe80::1456:f9ff:fe06:6228/64 scope link
> >valid_lft forever preferred_lft forever
> >
> >
> >
> > dag.sonst...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>
> --
>
> Andrija Panić
>


-- 

Andrija Panić

答复: Cloudstack-agent gets the local IP address exception

[li jerry]

Hi Andrija



  Your method is very good. I just tested agent. lb. When management fails, 
the agent can complete switching in a very short time.






发件人: Andrija Panic 
发送时间: Tuesday, April 23, 2019 10:22:47 PM
收件人: dev
抄送: us...@cloudstack.apache.org
主题: Re: Cloudstack-agent gets the local IP address exception

Hi Jerry,

not a good idea, if you don't mind me saying that.

Are you using 4.11 release ? If so you should use the internal LB logic
that is now part of Agent on KVM side - please check this one:
https://www.shapeblue.com/software-based-agent-lb-for-cloudstack/

Let me know if this works for you.

Best,
Andrija

On Tue, 23 Apr 2019 at 14:59, li jerry  wrote:

> HI Dag Sonstebo
>
> We deploy management and agent on the same host, with three such nodes.
> So we need to deploy keepalived on these three nodes, elect a VIP, and let
> all agents communicate with this VIP.
>
> 发件人: Dag Sonstebo
> 发送时间: 2019年4月23日 17:08
> 收件人: us...@cloudstack.apache.org;
> dev@cloudstack.apache.org
> 主题: Re: Cloudstack-agent gets the local IP address exception
>
> Li,
>
> Why do you run with this configuration? If this is for network resilience
> you would run a bond/team, not keepalived.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> On 22/04/2019, 14:37, "li jerry"  wrote:
>
> HI All
>
>
> my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via
> keepalived.
>
> After I started the cloudstack-agent, I got vip[10.226.16.10] and I
> couldn't get the correct IP [10.226.16.11];
>
> Can I have any way to get the cloudstack agent to get the correct IP
> address?
>
>
>
> Cloudstack 4.11.2
> CentOS 7.5
>
>
>
> br2:  mtu 1500 qdisc noqueue state UP
> group default qlen 1000
> link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
> inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute
> br2
>valid_lft forever preferred_lft forever
> inet 10.226.16.10/24 scope global secondary br2
>valid_lft forever preferred_lft forever
> inet6 fe80::1456:f9ff:fe06:6228/64 scope link
>valid_lft forever preferred_lft forever
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

--

Andrija Panić

Re: Cloudstack-agent gets the local IP address exception

[Andrija Panic]

Hi Jerry,

not a good idea, if you don't mind me saying that.

Are you using 4.11 release ? If so you should use the internal LB logic
that is now part of Agent on KVM side - please check this one:
https://www.shapeblue.com/software-based-agent-lb-for-cloudstack/

Let me know if this works for you.

Best,
Andrija

On Tue, 23 Apr 2019 at 14:59, li jerry  wrote:

> HI Dag Sonstebo
>
> We deploy management and agent on the same host, with three such nodes.
> So we need to deploy keepalived on these three nodes, elect a VIP, and let
> all agents communicate with this VIP.
>
> 发件人: Dag Sonstebo
> 发送时间: 2019年4月23日 17:08
> 收件人: us...@cloudstack.apache.org;
> dev@cloudstack.apache.org
> 主题: Re: Cloudstack-agent gets the local IP address exception
>
> Li,
>
> Why do you run with this configuration? If this is for network resilience
> you would run a bond/team, not keepalived.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> On 22/04/2019, 14:37, "li jerry"  wrote:
>
> HI All
>
>
> my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via
> keepalived.
>
> After I started the cloudstack-agent, I got vip[10.226.16.10] and I
> couldn't get the correct IP [10.226.16.11];
>
> Can I have any way to get the cloudstack agent to get the correct IP
> address?
>
>
>
> Cloudstack 4.11.2
> CentOS 7.5
>
>
>
> br2:  mtu 1500 qdisc noqueue state UP
> group default qlen 1000
> link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
> inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute
> br2
>valid_lft forever preferred_lft forever
> inet 10.226.16.10/24 scope global secondary br2
>valid_lft forever preferred_lft forever
> inet6 fe80::1456:f9ff:fe06:6228/64 scope link
>valid_lft forever preferred_lft forever
>
>
>
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>

-- 

Andrija Panić

答复: 答复: Cloudstack-agent gets the local IP address exception

[li jerry]

Hi Dag Sonstebo

Because we only have three servers in total, we can't make one management node 
independently, so we can only downgrade and let them merge.




发件人: Dag Sonstebo
发送时间: 2019年4月23日 21:35
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: 答复: Cloudstack-agent gets the local IP address exception

Hi Li,

Your configuration goes against best practice - you generally always keep 
management and hypervisors separate. To my knowledge there is nothing in the 
CloudStack KVM agent which will allow for the configuration you have in place, 
so you would have to deploy your own manual workarounds for this.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 23/04/2019, 13:59, "li jerry"  wrote:

HI Dag Sonstebo

We deploy management and agent on the same host, with three such nodes.
So we need to deploy keepalived on these three nodes, elect a VIP, and let 
all agents communicate with this VIP.

发件人: Dag Sonstebo
发送时间: 2019年4月23日 17:08
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: Cloudstack-agent gets the local IP address exception

Li,

Why do you run with this configuration? If this is for network resilience 
you would run a bond/team, not keepalived.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 22/04/2019, 14:37, "li jerry"  wrote:

HI All


my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via 
keepalived.

After I started the cloudstack-agent, I got vip[10.226.16.10] and I 
couldn't get the correct IP [10.226.16.11];

Can I have any way to get the cloudstack agent to get the correct IP 
address?



Cloudstack 4.11.2
CentOS 7.5



br2:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute 
br2
   valid_lft forever preferred_lft forever
inet 10.226.16.10/24 scope global secondary br2
   valid_lft forever preferred_lft forever
inet6 fe80::1456:f9ff:fe06:6228/64 scope link
   valid_lft forever preferred_lft forever



dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue






dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: 答复: Cloudstack-agent gets the local IP address exception

[Dag Sonstebo]

Hi Li,

Your configuration goes against best practice - you generally always keep 
management and hypervisors separate. To my knowledge there is nothing in the 
CloudStack KVM agent which will allow for the configuration you have in place, 
so you would have to deploy your own manual workarounds for this.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 23/04/2019, 13:59, "li jerry"  wrote:

HI Dag Sonstebo

We deploy management and agent on the same host, with three such nodes.
So we need to deploy keepalived on these three nodes, elect a VIP, and let 
all agents communicate with this VIP.

发件人: Dag Sonstebo
发送时间: 2019年4月23日 17:08
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: Cloudstack-agent gets the local IP address exception

Li,

Why do you run with this configuration? If this is for network resilience 
you would run a bond/team, not keepalived.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 22/04/2019, 14:37, "li jerry"  wrote:

HI All


my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via 
keepalived.

After I started the cloudstack-agent, I got vip[10.226.16.10] and I 
couldn't get the correct IP [10.226.16.11];

Can I have any way to get the cloudstack agent to get the correct IP 
address?



Cloudstack 4.11.2
CentOS 7.5



br2:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute 
br2
   valid_lft forever preferred_lft forever
inet 10.226.16.10/24 scope global secondary br2
   valid_lft forever preferred_lft forever
inet6 fe80::1456:f9ff:fe06:6228/64 scope link
   valid_lft forever preferred_lft forever



dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue






dag.sonst...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

答复: Cloudstack-agent gets the local IP address exception

[li jerry]

HI Dag Sonstebo

We deploy management and agent on the same host, with three such nodes.
So we need to deploy keepalived on these three nodes, elect a VIP, and let all 
agents communicate with this VIP.

发件人: Dag Sonstebo
发送时间: 2019年4月23日 17:08
收件人: us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
主题: Re: Cloudstack-agent gets the local IP address exception

Li,

Why do you run with this configuration? If this is for network resilience you 
would run a bond/team, not keepalived.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 22/04/2019, 14:37, "li jerry"  wrote:

HI All


my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via 
keepalived.

After I started the cloudstack-agent, I got vip[10.226.16.10] and I 
couldn't get the correct IP [10.226.16.11];

Can I have any way to get the cloudstack agent to get the correct IP 
address?



Cloudstack 4.11.2
CentOS 7.5



br2:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute br2
   valid_lft forever preferred_lft forever
inet 10.226.16.10/24 scope global secondary br2
   valid_lft forever preferred_lft forever
inet6 fe80::1456:f9ff:fe06:6228/64 scope link
   valid_lft forever preferred_lft forever



dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: Latest Qemu KVM EV appears to be broken with ACS

[Rohit Yadav]

All,


I've found and fixed an edge/security case while testing it for CentOS6, the PR 
should not be compatible for all support KVM distros:

https://github.com/apache/cloudstack/pull/3278


The issue was that the systemvm.iso file includes an authorized_keys file from 
our codebase and may overwrite the payload we send using patchviasocket or 
virsh qemu-guest-agent. I've removed that unknown/default authorized_keys file 
in the PR.


Historically, we had seen few cases where a VR failed to start with an error 
related to get_systemvm_template.sh execution (failing with a non-zero exit 
code) that finds the DomR version seen in logs. That issue would be fixed by my 
patch now.


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Simon Weller 
Sent: Tuesday, April 23, 2019 12:59:00 AM
To: dev@cloudstack.apache.org
Subject: Re: Latest Qemu KVM EV appears to be broken with ACS

Hey  Andrija,

In our case the SystemVMs were booting fine, but ACS wasn't able to inject the 
payload via the socket.

-Si


From: Andrija Panic 
Sent: Monday, April 22, 2019 1:16 PM
To: dev
Subject: Re: Latest Qemu KVM EV appears to be broken with ACS

Hi Simon, all,

did you try running CentOS with newer kernel - I just got a really strange
issue after upgrading KVM host from stock 1.5.3 to qemu-kvm-ev 2.12 with
stock kernel 3.10 (issues on Intel CPUs, while no issues on AMD Opteron),
which was fixed by upgrading kernel to 4.4 (Elrepo version).

My case was that SystemVM were not able to boot, stuck on "booting from
hard drive" SeaBios message (actually any VM with VirtIO "hardware") using
qemu-kvm-ev 2.12 (while no issues on stock 1.5.3).

What I could find is the that there are obviously some issues when using
nested KVM on top of ESXi (or HyperV), which is what I'm running.
When I switched template to Intel emulated one i.e. "Windows 2016" OS type
- VMs were able to boot just fine (user VM at least).

Might be related to original issue on this thread...

Best,
Andrija


rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

On Thu, 18 Apr 2019 at 22:36, Sven Vogel  wrote:

> Hi Rohit,
>
> Thx we will test it!
>
>
>
> Von meinem iPhone gesendet
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK RZ GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 11
> F +49 341 42649 - 18
> s.vo...@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer
> Registergericht: Leipzig HRB 17023
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 18.04.2019 um 21:44 schrieb Rohit Yadav :
> >
> > I've sent a PR that attempts to solve the issue. It is under testing but
> ready for review: https://github.com/apache/cloudstack/pull/3278
> >
> >
> > Thanks.
> >
> >
> > Regards,
> >
> > Rohit Yadav
> >
> > Software Architect, ShapeBlue
> >
> > https://www.shapeblue.com
> >
> > 
> > From: Simon Weller 
> > Sent: Monday, April 15, 2019 7:24:40 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: Latest Qemu KVM EV appears to be broken with ACS
> >
> > +1 for the qemu guest agent approach.
> >
> >
> > 
> > From: Wido den Hollander 
> > Sent: Saturday, April 13, 2019 2:32 PM
> > To: dev@cloudstack.apache.org; Rohit Yadav
> > Subject: Re: Latest Qemu KVM EV appears to be broken with ACS
> >
> >
> >
> >> On 4/12/19 9:33 PM, Rohit Yadav wrote:
> >> Thanks, I was already exploring a solution using qemu guest agent since
> morning today. It just so happened that you also thought of the approach,
> and I could validate my script to work with qemu ev 2.12 by the end of my
> day.
> >>
> >
> > That would be great actually. The Qemu Guest Agent is a lot better to
> > use. We might want to explore that indeed. Not for now, but it is a
> > better 

Re: Cross cluster cold migration failed in vmware

[Suresh Kumar Anaparti]

Hi Alireza

You can create similar compute offering with host tags (of hosts in a
cluster to start VM) and change the compute offering for the VM to the new
one.

- Suresh

On Tue, Apr 23, 2019 at 2:49 PM Alireza Eskandari 
wrote:

> Hi guys,
> I face with a problem in old migration of VMs between 2 cluster.
> If you stop a VM in 1st cluster, then you try to start it on a host in 2nd
> cluster, you will get "The specified key, name, or identifier already
> exists." error from VMWare.
> I have opened an issue in CloudStack github about it:
> https://github.com/apache/cloudstack/issues/3285
> I'm looking for a workaround. How can I prevent CloudStack to start VM in
> other clusters?
> Regards
>

Cross cluster cold migration failed in vmware

[Alireza Eskandari]

Hi guys,
I face with a problem in old migration of VMs between 2 cluster.
If you stop a VM in 1st cluster, then you try to start it on a host in 2nd
cluster, you will get "The specified key, name, or identifier already
exists." error from VMWare.
I have opened an issue in CloudStack github about it:
https://github.com/apache/cloudstack/issues/3285
I'm looking for a workaround. How can I prevent CloudStack to start VM in
other clusters?
Regards

Re: Cloudstack-agent gets the local IP address exception

[Dag Sonstebo]

Li,

Why do you run with this configuration? If this is for network resilience you 
would run a bond/team, not keepalived.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 22/04/2019, 14:37, "li jerry"  wrote:

HI All


my kvm host [ip:10.226.16.11] virtualized a vip[10.226.16.10] via 
keepalived.

After I started the cloudstack-agent, I got vip[10.226.16.10] and I 
couldn't get the correct IP [10.226.16.11];

Can I have any way to get the cloudstack agent to get the correct IP 
address?



Cloudstack 4.11.2
CentOS 7.5



br2:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether ac:1f:6b:ba:96:ea brd ff:ff:ff:ff:ff:ff
inet 10.226.16.11/24 brd 10.226.16.255 scope global noprefixroute br2
   valid_lft forever preferred_lft forever
inet 10.226.16.10/24 scope global secondary br2
   valid_lft forever preferred_lft forever
inet6 fe80::1456:f9ff:fe06:6228/64 scope link
   valid_lft forever preferred_lft forever



dag.sonst...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue