date:20190423

CLOUDSTACK COLLABORATION CONFERENCE 2019 - LAS VEGAS

2019-04-23 Thread 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

2019-04-23 Thread 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
> 抄送: users@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
> > 收件人: users@cloudstack.apache.org;
> > d...@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

2019-04-23 Thread li jerry

Hi Swen



  Now our new environment is only three computing node servers, no other 
resources, so I can not but think of other solutions.






发件人: Swen - swen.io 
发送时间: Tuesday, April 23, 2019 10:31:31 PM
收件人: users@cloudstack.apache.org
主题: AW: 答复: Cloudstack-agent gets the local IP address exception

Hi Li,

you can use a VM on another server for management, it does not need to be a 
physical server. Bit this VM needs to be not on the 3 servers which you are 
going to use for your Cloudstack VMs.
If you have any hypervisor outside of the 3 physical servers, than install the 
management server there.

cu Swen

-Ursprüngliche Nachricht-
Von: li jerry 
Gesendet: Dienstag, 23. April 2019 16:01
An: d...@cloudstack.apache.org; users@cloudstack.apache.org
Betreff: 答复: 答复: Cloudstack-agent gets the local IP address exception

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
收件人: users@cloudstack.apache.org; 
d...@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
收件人: users@cloudstack.apache.org; 
d...@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

2019-04-23 Thread 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
抄送: users@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
> 收件人: users@cloudstack.apache.org;
> d...@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ć

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

2019-04-23 Thread Swen - swen.io

Hi Li,

you can use a VM on another server for management, it does not need to be a 
physical server. Bit this VM needs to be not on the 3 servers which you are 
going to use for your Cloudstack VMs.
If you have any hypervisor outside of the 3 physical servers, than install the 
management server there.

cu Swen

-Ursprüngliche Nachricht-
Von: li jerry  
Gesendet: Dienstag, 23. April 2019 16:01
An: d...@cloudstack.apache.org; users@cloudstack.apache.org
Betreff: 答复: 答复: Cloudstack-agent gets the local IP address exception

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
收件人: users@cloudstack.apache.org; 
d...@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
收件人: users@cloudstack.apache.org; 
d...@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

2019-04-23 Thread 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
> 收件人: users@cloudstack.apache.org;
> d...@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

2019-04-23 Thread 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
收件人: users@cloudstack.apache.org; 
d...@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
收件人: users@cloudstack.apache.org; 
d...@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

2019-04-23 Thread 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
收件人: users@cloudstack.apache.org; 
d...@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

2019-04-23 Thread 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
收件人: users@cloudstack.apache.org; 
d...@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

AW: Resource type for an ACL? (API)

2019-04-23 Thread peter.muryshkin

Hi, all,

here a follow-up on ACL tagging.

Following Andrea's suggestion:

>> I think you may be looking at "create tags resourcetype=networkacl  "

we have now some tests but I must admit I am not sure about the following 
things:

- is it possible to tag both single ACL items like FirewallRules or just 
ACLLists?
- what is the exact spelling of their resource types?

I have tried the following as domain master user:

- tag ACL item using resource type spelling "NetworkACL"
- tag ACL item using resource type spelling "NetworkAcl"

Here the system says, "530 - Does not have permission to operate in this 
domain". Where could be this permission set given it is generally possible to 
tag resources you can create and delete yourself?

- then, tag an ACL list using resource type "NetworkACL". Here the system says, 
it can't match given ID and resource type.

- finally, tag an ACL list using resource type "NetworkACLList". In this case I 
get the error "The resource type NetworkACLList doesn't support resource tags".

Test code (includes also a unit test to tag a NAT network which passes):
https://github.com/pmury/acs-uat/blob/master/test/test_tags.py

kind regards
Peter 





kind regards
Peter














Von: Anurag A [anuraga.i...@gmail.com]
Gesendet: Freitag, 5. April 2019 12:45
An: users@cloudstack.apache.org
Cc: anurag.awas...@shapeblue.com
Betreff: Re: Resource type for an ACL? (API)

Typo - Just to clarify - you are able to create tags as root admin and
domain admins but not as user?


On Fri, Apr 5, 2019 at 4:11 PM Anurag A  wrote:

> Hi Peter,
>
> Just to clarify - you unable to create tags as root admin and domain
> admins but not as user?
>
> That seems expected and there are some open issues around that too -
> https://github.com/apache/cloudstack/issues/2823
>
> May be someone else has more inputs on this so you can wait for their
> response.
>
> Thanks!
> Regards,
> Anurag
>
> On Fri, Apr 5, 2019 at 3:20 PM  wrote:
>
>>
>> Hi, Anurag,
>>
>> thank you for your quick response - as I've found out, I am actually NOT
>> able to create a tag.
>>
>> Error message:
>> "The user is not allowed to request the API command or the API command
>> does not exist"
>>
>> But, I tried it as a root user of an account - is tagging then allowed
>> for the global root admin only?
>>
>> Call:
>> result = self.cs.create_tags(resourceids=self.firewallruleid,
>> resourcetype='FirewallRule', tags = {'foo':'bar'})
>>
>> kind regards
>> Peter
>>
>> 
>> Von: Anurag Awasthi [anurag.awas...@shapeblue.com]
>> Gesendet: Freitag, 5. April 2019 07:04
>> An: Muryshkin, Peter; users@cloudstack.apache.org
>> Betreff: Re: Resource type for an ACL? (API)
>>
>> Hi Peter,
>>
>> Welcome to the community!
>>
>> I think you may be looking at "create tags resourcetype=networkacl  "
>> call.
>>
>> Kind Regards,
>> Anurag
>>
>> anurag.awas...@shapeblue.com
>> www.shapeblue.com
>> @shapeblue
>>
>>
>>
>>
>> 
>> From: peter.murysh...@zv.fraunhofer.de 
>> Sent: Thursday, April 4, 2019 8:31 PM
>> To: users@cloudstack.apache.org
>> Subject: Resource type for an ACL? (API)
>>
>> Hi, all,
>>
>> while I can create a tag for a firewall rule, I can't find the resource
>> name for network ACL item.
>>
>> Is it anyhow possible to set a tag there?
>>
>>
>> P.S. This is my first time I post to this mailing list, so hello
>> everybody - Apache CloudStack is really great and from the first impression
>> the community seems to be very enjoyable!
>>
>> kind regards
>> Peter
>>
>>
>>

Re: Cloudstack-agent gets the local IP address exception

2019-04-23 Thread 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

CLOUDSTACK COLLABORATION CONFERENCE 2019 - LAS VEGAS

Re: Cloudstack-agent gets the local IP address exception

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

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

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

Re: Cloudstack-agent gets the local IP address exception

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

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

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

AW: Resource type for an ACL? (API)

Re: Cloudstack-agent gets the local IP address exception

11 matches

Site Navigation

Mail list logo

Footer information