RE: [VOTE] next version 20 instead of 4.20

[Paul Angus]

Hi Rohit, thank you

So to recap;

Semantic versioning goes (in our use):
 .  .  . 


And as I understand it you're looking to go

 .  . 
Starting from 20

I'd ask the question - are there any big/disruptive changes people would want 
to bundle together to keep the semantic versioning and move to 5.x.y.z

I'm assuming not, so the move proposed is to drop semantic versioning and 
continue from 20, understanding that we would lose the mechanism to warn of 
very disruptive changes (for what it's worth).

I've no objection to it.  The issue was, that reading the thread, people had 
different takes on what the change was, what would it do and what it meant. And 
also incorrect understandings of semantic versioning.

So, to be pedantic, and have a clearly defined vote, I'd change the vote to 
something like "Drop semantic versioning and continue from 20".  And include 
your explanation about moving to
 .  . 

I would be ok to +1 that ^^^

-paul 

-Original Message-
From: Rohit Yadav  
Sent: Tuesday, March 5, 2024 4:02 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [VOTE] next version 20 instead of 4.20

As I understand Daan's vote proposal and from the previous discussion thread, 
the current scheme that results in a release like 4.20.x.y would simply become 
20.a.b, wherein "a" is for maintenance release (counter, starting with 0) and 
"b" is only used for security releases (counter, starting with 0).

The voting thread is about "deciding to drop the 4 from our versioning scheme", 
wherein the next CloudStack version would become "20" instead of "4.20". By 
agreeing to drop the "4" I think we're effectively voting and agreeing that 
we'll not be breaking APIs. Some other opensource projects have done something 
similar too. Of course, this needs to be properly explained and documented both 
by a blog article and on the project wiki.

Paul - are you satisfied with the explanations and discussions, are you still 
blocking this vote thead or do you want to reconsider your vote?


Regards.

 



From: Paul Angus 
Sent: Tuesday, February 20, 2024 15:55
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: RE: [VOTE] next version 20 instead of 4.20

Hi Daan,


>From our wiki page:

-- Quote
For those that may not be familiar with Semantic Versioning, the number format 
is: X.Y.Z, where X is the major version, Y is the minor version, Z is the patch 
number. The community strives to ensure backward API compatibility within each 
major version (i.e.: code written against the CloudStack 4.0.0-incubating API 
should work with all future 4.y.z versions). The community may decide to 
increment the major version number in situations where underlying 
implementation details require a cloud operator to face significant challenges 
in upgrading from one version to the next. This should be rare situation.

In practice, feature releases will normally be an increment of the minor 
version number of the project. Feature releases that break backward 
compatibility will cause the major version number to be incremented. Bug fix 
releases will never increment anything except the patch number.
-- End quote.


Specifically:
The community may decide to increment the major version number in situations 
where underlying implementation details require a cloud operator to face 
significant challenges in upgrading from one version to the next. This should 
be rare situation.


>From this I can't see how we have broken the versioning.  Have we introduced 
>anything that meets the criteria above?  Again, the term 'minor version' is an 
>unfortunate one because it makes it sound like it wouldn’t contain big new 
>features.  However, that isn't the case, it can and should.

Also, I'd like to see fully laid out for the next few versions, how versioning 
is proposed to work, and what each part of x.y.z.n is then going to denote.

- Paul

-Original Message-
From: Daan Hoogland 
Sent: Tuesday, February 20, 2024 10:05 AM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: [VOTE] next version 20 instead of 4.20

Vivek, we could, but the main idea is that we repair our versioning system and 
make clear how we are actually dealing with our current system, which is major 
- new , possibly breaking features minor - improvements and enhancements tiny - 
urgent (security) fixes

and in addition we would go to 20 to indicate that is the follower of
4.19 not of 4. Someone may implement a new cloudstack (cloudstack5 for
instance) but this would not have anything to do with our current versioning 
system.

On Tue, Feb 20, 2024 at 5:06 AM Vivek Kumar  
wrote:
>
> Why not 5.0 ? Then it will be like 5.1, 5.2 in the future.  Just asking ..!
>
>
> > On 19-Feb-2024, at 10:49 PM, Paul Angus  wrote:
> >
> > Hi Daan,
> >

RE: [VOTE] next version 20 instead of 4.20

[Paul Angus]

Hi Daan,


>From our wiki page:

-- Quote
For those that may not be familiar with Semantic Versioning, the number format 
is: X.Y.Z, where X is the major version, Y is the minor version, Z is the patch 
number. The community strives to ensure backward API compatibility within each 
major version (i.e.: code written against the CloudStack 4.0.0-incubating API 
should work with all future 4.y.z versions). The community may decide to 
increment the major version number in situations where underlying 
implementation details require a cloud operator to face significant challenges 
in upgrading from one version to the next. This should be rare situation.

In practice, feature releases will normally be an increment of the minor 
version number of the project. Feature releases that break backward 
compatibility will cause the major version number to be incremented. Bug fix 
releases will never increment anything except the patch number.
-- End quote.


Specifically:
The community may decide to increment the major version number in situations 
where underlying implementation details require a cloud operator to face 
significant challenges in upgrading from one version to the next. This should 
be rare situation.


>From this I can't see how we have broken the versioning.  Have we introduced 
>anything that meets the criteria above?  Again, the term 'minor version' is an 
>unfortunate one because it makes it sound like it wouldn’t contain big new 
>features.  However, that isn't the case, it can and should.

Also, I'd like to see fully laid out for the next few versions, how versioning 
is proposed to work, and what each part of x.y.z.n is then going to denote.

- Paul

-Original Message-
From: Daan Hoogland  
Sent: Tuesday, February 20, 2024 10:05 AM
To: users@cloudstack.apache.org
Cc: d...@cloudstack.apache.org
Subject: Re: [VOTE] next version 20 instead of 4.20

Vivek, we could, but the main idea is that we repair our versioning system and 
make clear how we are actually dealing with our current system, which is major 
- new , possibly breaking features minor - improvements and enhancements tiny - 
urgent (security) fixes

and in addition we would go to 20 to indicate that is the follower of
4.19 not of 4. Someone may implement a new cloudstack (cloudstack5 for
instance) but this would not have anything to do with our current versioning 
system.

On Tue, Feb 20, 2024 at 5:06 AM Vivek Kumar  
wrote:
>
> Why not 5.0 ? Then it will be like 5.1, 5.2 in the future.  Just asking ..!
>
>
> > On 19-Feb-2024, at 10:49 PM, Paul Angus  wrote:
> >
> > Hi Daan,
> >
> > Can you clarify what we are actually voting on please.
> >
> > In thread that is linked I've seen:
> >
> > "[the vote] will be to adjust to the semantic versioning system."
> > - you can't go to 20 AND keep semantic versioning. The act of going to 20 
> > breaks semantic versioning [1].
> >
> > " drop the 4 at version 20 and continue as usual with minor and patch level 
> > updates as we have in the past."
> > - what's supposed to come next ? in lieu of what would have been 4.21 will 
> > it be 21 ?  is it going to be 20.1 then 20.2 ?
> >
> > From the thread and how people are referring to 'minor versions', there is 
> > a misunderstanding as to what semantic versioning means. For our project 
> > its explained here [1].   Major versions meaning "probably going to break a 
> > load of people's stuff', with minor versions not breaking stuff (at least 
> > not on purpose). So I get calling them minor versions really underplays the 
> > changes it can hold.
> >
> >
> > I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think 
> > the vote should be on 'A change to the version numbering scheme' and then 
> > what is proposed properly laid out.
> >
> >
> >
> >
> > [1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases 
> > (section on versioning about 2/3 down)
> >
> > -Original Message-
> > From: Daan Hoogland 
> > Sent: Monday, February 19, 2024 12:50 PM
> > To: dev 
> > Cc: users 
> > Subject: [VOTE] next version 20 instead of 4.20
> >
> > LS,
> >
> > This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be 
> > counted please reply to dev@.
> >
> > As discussed in [1] we are deciding to drop the 4 from our versioning 
> > scheme. The result would be that the next major version will be 20 instead 
> > of 4.20, as it would be in a traditional upgrade. As 20 > 4 and the 
> > versions are processed numerically there are no technical impediments.
> >
> > +1 agree (next major version as 20
> > 0 (no opinion)
> > -1 disagree (k

RE: [VOTE] next version 20 instead of 4.20

[Paul Angus]

Hi Daan,

Can you clarify what we are actually voting on please.

In thread that is linked I've seen:

"[the vote] will be to adjust to the semantic versioning system."
- you can't go to 20 AND keep semantic versioning. The act of going to 20 
breaks semantic versioning [1].

" drop the 4 at version 20 and continue as usual with minor and patch level 
updates as we have in the past."
- what's supposed to come next ? in lieu of what would have been 4.21 will it 
be 21 ?  is it going to be 20.1 then 20.2 ?

>From the thread and how people are referring to 'minor versions', there is a 
>misunderstanding as to what semantic versioning means. For our project its 
>explained here [1].   Major versions meaning "probably going to break a load 
>of people's stuff', with minor versions not breaking stuff (at least not on 
>purpose). So I get calling them minor versions really underplays the changes 
>it can hold.


I'm going to stick in a -1.  Not as hard 'no' to any changes, but I think the 
vote should be on 'A change to the version numbering scheme' and then what is 
proposed properly laid out.  




[1]   https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases (section 
on versioning about 2/3 down)

-Original Message-
From: Daan Hoogland  
Sent: Monday, February 19, 2024 12:50 PM
To: dev 
Cc: users 
Subject: [VOTE] next version 20 instead of 4.20

LS,

This is a vote on dev@c.a.o with cc to users@c.a.o. If you want to be counted 
please reply to dev@.

As discussed in [1] we are deciding to drop the 4 from our versioning scheme. 
The result would be that the next major version will be 20 instead of 4.20, as 
it would be in a traditional upgrade. As 20 > 4 and the versions are processed 
numerically there are no technical impediments.

+1 agree (next major version as 20
0 (no opinion)
-1 disagree (keep 4.20 as the next version, give a reason)

As this is a lazy consensus vote any -1 should be accompanied with a reason.

[1] https://lists.apache.org/thread/lh45w55c3jmhm7w2w0xgdvlw78pd4p87

--
Daan

IMPORTANT FROM ASF LEGAL - Use of Generative AI tools

[Paul Angus]

Hi All,

 

This has been shared by the ASF's Legal Committee regarding the use of AI in
Apache projects.  If you are or plan to use AI tools to help with your
commits (code or otherwise) please take the time to read it.

 

https://www.apache.org/legal/generative-tooling.html

 

 

 

Kind regards

 

Paul Angus

 

Daan Hoogland - New ASF Member

[Paul Angus]

 

It is my pleasure to announce that Daan Hoogland as been elected to become a
member of the ASF.

The ASF would like to recognize both his practical involvement and the way
in which he has interacted with others in and around the ASF.

 

Congratulations  Daan.

 

 

 

 

Kind regards

 

Paul Angus

 

RE: [DISCUSS] Github Discussions for CloudStack?

[Paul Angus]

Thank you for confirming what I said about the ASFs requirements around mailing 
lists.

However, having primary and secondary places to look for threads could make it 
harder for users to find answers to questions that have been asked before; so 
I'm asking that this issue be considered fully so that we can ensure that we 
support users as best we can.


Kind Regards


Paul Angus

-Original Message-
From: Rohit Yadav  
Sent: Monday, December 19, 2022 4:16 PM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] Github Discussions for CloudStack?

Update, tl;dr - ASF infra has allowed the use of Github Discussions only for 
user queries and not development and this is because they don't have two-way 
mirroring of the same enabled on mailing lists (yet). This is also not 
enabled/controlled via asf yaml yet and must be requested once project consesus 
is reached 
(https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions).

My understanding (based on interactions with ASF infra) is that mailing lists 
are recognised medium to be used by ASF projects for development [1], and users 
mailing lists exist for users as primary support channels but not mandatory. 
This is also why ASF infra is allowing Github Discussions for only user queries 
- they wouldn't enable something for a project that isn't ASF compliant.

I think it could be a good idea to try Github Discussions as means of providing 
support, one specific thing I like about Github Discussions is the 
classification of user queries as Q, for example:
https://github.com/apache/airflow/discussions/categories/q-a
https://github.com/apache/superset/discussions/categories/q-a-help

[1] https://www.apache.org/foundation/mailinglists.html


Regards.


From: Paul Angus 
Sent: Sunday, December 18, 2022 18:45
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: RE: [DISCUSS] Github Discussions for CloudStack?

If this makes discussions more accessible, it could be a good thing.

However, as mentioned by Daniel and Nux, unless there is a two-way mirror of 
discussions on mailing lists and Github discussions, it's going to split 
everyone's attention, or double where anyone has to look for answers.

Mailing lists are the only medium recognised by the ASF, so any 'official' 
conversations must be had on, or replicated to, the mailing lists. The stats 
gathered by the ASF are also based on mailing list activity.

I think these guardrails need to be in place first before trying.

Alternatively, if the issue is simply that questions are popping up in Github 
that shouldn't really be there.  Then it would be much simpler to educate 
people and just point them to the mailing list whenever it happens.

Paul.

 


-Original Message-
From: David Jumani 
Sent: Thursday, December 15, 2022 3:21 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] Github Discussions for CloudStack?

Sounds like a good idea
+1 for giving it a try!

From: Rohit Yadav 
Sent: Wednesday, December 14, 2022 2:37 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [DISCUSS] Github Discussions for CloudStack?

All,

In the past, we had moved away from JIRA and ReviewBoard to Github as it 
provided a single platform for both the user and the dev community to 
collaborate on issues/requests and code changes (pull requests). We later 
organically started using Github for release milestones/triaging, recently 
projects. For sub-projects such as cloudstack-cloudmonkey, 
cloudstack-terraform-provider etc we also use the wiki features. More recently 
we're not advised to move to Github actions from Travis CI by ASF infra.

Off lately, several user-related discussions and questions that we would have 
expected on the users ML are finding ways in Github issues, which aren't issues 
per se but questions, and discussions. Should we explore, enable and try Github 
Discussions [1] for CloudStack repos?

Several Apache projects have enabled Github Discussions [1], for example:
https://github.com/apache/couchdb/discussions
https://github.com/apache/apisix/discussions
https://github.com/apache/shardingsphere/discussions
https://github.com/apache/streampipes/discussions
https://github.com/apache/pulsar/discussions
https://github.com/apache/airflow/discussions
https://github.com/apache/dolphinscheduler/discussions
https://github.com/apache/inlong/discussions
https://github.com/apache/doris/discussions
https://github.com/apache/arrow-datafusion/discussions
https://github.com/apache/superset/discussions

[1] https://github.com/features/discussions


Regards.

RE: [DISCUSS] Github Discussions for CloudStack?

[Paul Angus]

If this makes discussions more accessible, it could be a good thing.

However, as mentioned by Daniel and Nux, unless there is a two-way mirror of 
discussions on mailing lists and Github discussions, it's going to split 
everyone's attention, or double where anyone has to look for answers.

Mailing lists are the only medium recognised by the ASF, so any 'official' 
conversations must be had on, or replicated to, the mailing lists. The stats 
gathered by the ASF are also based on mailing list activity.

I think these guardrails need to be in place first before trying.

Alternatively, if the issue is simply that questions are popping up in Github 
that shouldn't really be there.  Then it would be much simpler to educate 
people and just point them to the mailing list whenever it happens.

Paul.

-Original Message-
From: David Jumani  
Sent: Thursday, December 15, 2022 3:21 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: [DISCUSS] Github Discussions for CloudStack?

Sounds like a good idea
+1 for giving it a try!

From: Rohit Yadav 
Sent: Wednesday, December 14, 2022 2:37 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: [DISCUSS] Github Discussions for CloudStack?

All,

In the past, we had moved away from JIRA and ReviewBoard to Github as it 
provided a single platform for both the user and the dev community to 
collaborate on issues/requests and code changes (pull requests). We later 
organically started using Github for release milestones/triaging, recently 
projects. For sub-projects such as cloudstack-cloudmonkey, 
cloudstack-terraform-provider etc we also use the wiki features. More recently 
we're not advised to move to Github actions from Travis CI by ASF infra.

Off lately, several user-related discussions and questions that we would have 
expected on the users ML are finding ways in Github issues, which aren't issues 
per se but questions, and discussions. Should we explore, enable and try Github 
Discussions [1] for CloudStack repos?

Several Apache projects have enabled Github Discussions [1], for example:
https://github.com/apache/couchdb/discussions
https://github.com/apache/apisix/discussions
https://github.com/apache/shardingsphere/discussions
https://github.com/apache/streampipes/discussions
https://github.com/apache/pulsar/discussions
https://github.com/apache/airflow/discussions
https://github.com/apache/dolphinscheduler/discussions
https://github.com/apache/inlong/discussions
https://github.com/apache/doris/discussions
https://github.com/apache/arrow-datafusion/discussions
https://github.com/apache/superset/discussions

[1] https://github.com/features/discussions


Regards.




 

RE: Update Rules for Default Roles

[Paul Angus]

Hi Ranjit,

This is by design. You need to create a copy of the Domain Admin role and 
modify that.  You can then assign the new version to accounts/users.

This is because the 'default' role changes as new APIs are added or modified.  
Having your own version gives you a fixed set of rules.



-Original Message-
From: Ranjit Jadhav  
Sent: Friday, April 22, 2022 6:05 AM
To: users@cloudstack.apache.org; dev 
Subject: Update Rules for Default Roles

Hello Folks,

I am getting the below error while trying to update Rules for Role Domain 
Admin, any suggestions on a workaround.

Request Failed (531)
Role permission cannot be added for Default roles

Any hint/solution will be of great help.

Thanks and regards,
Ranjit

RE: [SHARE] CAPC - Kubernetes CAPI Provider for Apache CloudStack

[Paul Angus]

Great, well done!

Kind Regards


Paul Angus

-Original Message-
From: Nux  
Sent: Monday, March 7, 2022 1:10 PM
To: d...@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: Re: [SHARE] CAPC - Kubernetes CAPI Provider for Apache CloudStack

Well done and thanks!

---
Nux!
www.nux.ro

On 2022-03-07 12:43, Rohit Yadav wrote:
> Hi all,
> 
> I thought everybody would like to know that my colleagues and I at 
> ShapeBlue have been recently working on a Kubernetes CAPI provider for 
> Apache CloudStack (CAPC,
> https://github.com/aws/cluster-api-provider-cloudstack) in a joint 
> collaboration with AWS (Amazon Web Services).
> 
> It is virtually finished and we’re in the process of donating the CAPC 
> provider [1] to CNCF licensed under Apache Public License v2. Further 
> development will be done under the Kubernetes Cluster Lifecycle SIG 
> community [2][3].
> 
> The Kubernetes Cluster API (https://cluster-api.sigs.k8s.io/)
> simplifies provisioning, upgrading, and operating multiple Kubernetes 
> clusters into specific target infrastructures using a consistent and 
> declarative way. A CAPI provider for Apache CloudStack makes 
> CloudStack one of those target infrastructures 
> (https://cluster-api.sigs.k8s.io/reference/providers.html).
> 
> The provider is ready for use and has gone through extensive testing 
> against CloudStack 4.14-4.16 across KVM, VMware, and XenServer/XCP-ng 
> hypervisors [6] and has passed the e2e as well as k8s conformance 
> tests.
> 
> After the donation of CAPC is complete, like other providers, we'll 
> work towards creating a proper docs website on how to participate, 
> collaborate, use and develop CAPC, work on installation and usage 
> guides and tutorial/training videos; for now, if anybody is interested 
> in a demo our David has created a 10-min video [4].
> 
> We would like to ask all of you for your support - testing the CAPC 
> provider and sending feedback – would also be interested in hearing if 
> people here will find this useful.
> 
> If anybody is interested in collaborating on the future development, 
> you may participate on the k8s sig-cluster-lifecycle mailing list 
> https://groups.google.com/g/kubernetes-sig-cluster-lifecycle and soon 
> you may join a new #cluster-api-cloudstack slack channel [5] under the 
> Kubernetes project slack (users/developers can get an invite via 
> http://slack.k8s.io, we've requested k8s project to create this new 
> slack channel which is pending approval [5]).
> 
> [1] https://github.com/aws/cluster-api-provider-cloudstack
> [2] https://github.com/kubernetes/org/issues/3279
> [3]
> https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/sg46hga
> IzJs/m/KcAqxSt5AQAJ
> [4]
> https://shapeblue-engineering-videos.s3.eu-west-1.amazonaws.com/capc/c
> apc-demo-acs416.mp4 [5] 
> https://github.com/kubernetes/community/pull/6427
> [6] http://download.cloudstack.org/templates/capi-test/
> 
> 
> Regards.

RE: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon Weller

[Paul Angus]

Yes,

Same from me, thank you Gabriel, and congratulations Simon.

Kind Regards


Paul Angus

-Original Message-
From: Suresh Kumar Anaparti  
Sent: Thursday, March 17, 2022 11:26 AM
To: dev ; users@cloudstack.apache.org
Cc:  
Subject: Re: [ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Simon 
Weller

Congratulations Simon!

Thank you Gabriel, for your work.

Regards,
Suresh

On Thu, Mar 17, 2022 at 4:27 PM Rohit Yadav  wrote:
>
> Congratulations Simon! And thank you Gabriel.
>
> Regards.
>
> On Thu, Mar 17, 2022 at 3:25 PM Gabriel Beims Bräscher 
>  wrote:
> >
> > Hello, all CloudStack community!
> >
> > It gives me great pleasure to announce that the ASF board last night 
> > accepted our PMC's nomination of Simon Weller as the next PMC Chair 
> > / VP of the Apache CloudStack project.
> >
> > I would like to thank everyone for the support I've received over the past 
> > year.
> > It was a great honor being the PMC Chair of this amazing project/community!
> >
> > To Simon, my sincere congratulations, and I wish you success in the new 
> > role!
> > Very well deserved!
> >
> > Please join me in congratulating Simon, the CloudStack PMC Chair / VP.
> >
> > Best Regards,
> > Gabriel Bräscher.

RE: How are you monitoring Cloudstack?

[Paul Angus]

Hi Nux,

At Ticketmaster we use the Prometheus exporter.  We about to work on adding
more detail to what's exported wrt to VMs, as it very infrastructure focused
out-of-the-box.



Kind regards

Paul Angus

-Original Message-
From: Nux  
Sent: 02 March 2022 10:56
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Subject: Re: How are you monitoring Cloudstack?

Hi!

Another nudge on the $subject in case people missed this.

If you have a functioning way of monitoring Cloudstack & co in your
organisation I'd like to hear about it.
It doesn't have to be anything exotic, so don't be shy as long as we have
anything to talk about.

Thanks :)


On 2022-02-21 14:38, Nux! wrote:
> Hi folks,
> 
> If anyone cares to share (on or off list) with me a few words about 
> how they are monitoring Cloudstack and related infrastructure that'd 
> be lovely.
> I'm trying to find out what are the choices currently and how we can 
> improve the overall experience.
> 
> Don't be shy!
> 
> Cheers

RE: Local simulation of Apache Cloudstack instances/API endpoints: state of the art, target groups and use cases

[Paul Angus]

Hi Peter,

I need to get round to polishing a dockerfile that would create an image to
be run as a CloudStack simulator in a container (or if there's enough
interest I could share it's current state for others to finish).

But. If you want to work on real world integrations, I'd guess that you
would likely to need real hosts to create VMs on. Trillian
(https://github.com/shapeblue/trillian) was created for the exact purpose
that you are describing.   In fact it runs most of the automated testing
done on CloudStack. And can support 10s even 100s of concurrent
environments.

I'm not going to lie - it takes a bit of setting up (and isn't local) - but
it's run thousands of times creating environments for testing business logic
and integrations


Regards

Paul Angus


-Original Message-
From: Muryshkin, Peter  
Sent: Thursday, October 21, 2021 11:30 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Local simulation of Apache Cloudstack instances/API endpoints:
state of the art, target groups and use cases

Hi all,

from what I can find, there are  three more or less established/already well
elaborated approaches to simulate a CloudStack instance locallly.
Depending on the target group and their goals, they can have different
levels of fidelity and usability.

1. Obviously CloudStack developers confgure a KVM development environment to
work inside it, this is part of the Apache CloudStack Hackerbook kindly
shared by ShapeBlue. [1] 2. For test scenarios, Hackerbook describes a
mocked simulator approach [2] 3. For users for whom the whole cloud system
is just a "black box", especially cloud beginners, there is a single
integrated Docker container. [3]

With the rise of CI/CD and infrastructure as code automation practices,
where you just need more or less on demand one or even many versions of the
CloudStack API,  [3] appears to be a crucial building block in the cloud
userspace before just "trying out CloudStack".

So it appears that there might be much demand on a Apache CloudStack
containerized instance:

1. Demand from potential new adopters, for their "Apache CloudStack to go"
demos 2. Demand from DevOps/GitOps/SRE/you-name-it enabled teams who
implement their virtual infrastructure for example with Terraform and the
CloudStack provider plugin and want to simulate rollout scenarios.

However, is this true?

* the container simulator hasn't been updated on DockerHub since a couple of
years; is there another place in meantime or will this approach dumped for
some reason?
* there is not so much discussion about this asset on mailing lists; so
there is not so much demand as one might assume?

What do you think?

kind regards

--

Peter Muryshkin
Fraunhofer Gesellschaft
https://www.linkedin.com/in/muryshkin/

Hi (Again)

[Paul Angus]

Hey All,

So, I’ve moved over to the Dark Side, and I’m now purely a user of CloudStack 
with Ticketmaster/Live Nation.  I’m mostly going to be all about breaking 
things rather than fixing them 

…Starting off with:  As root admin I can list all VMs including ones in 
projects via cmk -list virtualmachines projectid=-1
Is there a way to do the same in the UI?

Cheers!

Paul.

This message is confidential and may be legally privileged or otherwise 
protected from disclosure. If you are not the intended recipient, please 
telephone or email the sender and delete this message and any attachment from 
your system; you must not copy or disclose the contents of this message or any 
attachment to any other person. We may monitor email traffic and the content of 
internal and external messages sent to and from us to ensure compliance with 
internal policies and for the purposes of security.

Ticketmaster UK Limited. Registered Office: 30 St John Street, London EC1M 4AY. 
Registered in England and Wales. Company Number 02662632.

RE: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Paul Angus]

+1

Regards

Paul Angus

-Original Message-
From: Suresh Anaparti  
Sent: 11 May 2021 07:15
To: users@cloudstack.apache.org; d...@cloudstack.apache.org; 
priv...@cloudstack.apache.org
Subject: Re: [VOTE] Renaming default git branch name from 'master' to 'main' 
and replace offensive words as appropriate for inclusiveness

+1 , adding my vote as well.

Regards,
Suresh


 

On 07/05/21, 2:10 PM, "Harikrishna Patnala"  
wrote:

+1  from me.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Friday, April 30, 2021 5:13 PM
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [VOTE] Renaming default git branch name from 'master' to 'main' 
and replace offensive words as appropriate for inclusiveness

Hi All,

Following the discussion thread on renaming default git branch name and 
inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:

1. Accept the following rename PRs (raised against 'master' branch) which 
renames git default branch to 'main' and replaces some offensive words, and 
Merge them post acceptance.
- cloudstack => PR: https://github.com/apache/cloudstack/pull/4922
- cloudstack-documentation => PR: 
https://github.com/apache/cloudstack-documentation/pull/155
- cloudstack-www => PR: 
https://github.com/apache/cloudstack-www/pull/83
- cloudstack-cloudmonkey => PR: 
https://github.com/apache/cloudstack-cloudmonkey/pull/76
- cloudstack-kubernetes-provider => PR: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/29
- cloudstack-ec2stack => PR: 
https://github.com/apache/cloudstack-ec2stack/pull/2
- cloudstack-gcestack => PR: 
https://github.com/apache/cloudstack-gcestack/pull/3

2. Request ASF infra to disable pushes to 'master' branch.

3. Rename 'master' branch to 'main' [2][3], and Request ASF infra (open 
INFRA ticket) to make 'main' as the default branch [4], in GitHub repo settings 
for all the CloudStack repos. This will also re-target the current PRs against 
'master' branch to 'main'.

3a. The update on the central repo will be done as follows (only by a PMC 
or Infra member with access)
- Clone the repo (git clone 
https://github.com/apache/cloudstack.git)
- Sync local 'master' with the cloudstack repo (cd cloudstack && 
git checkout master && git fetch --all -p && git pull)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Push renamed 'main' branch (git push -u origin main)
- Update Default Branch on GitHub [4]
- Delete 'master' branch (git push origin --delete master)
3b. After the central renaming has been done. New users can clone and 
directly checkout 'main' branch. Existing users can start using 'main' locally, 
using the below steps.
- Switch to master branch (git checkout master)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Sync local 'main' with repo (git fetch)
- Remove the existing tracking connection with “origin/master” (git 
branch --unset-upstream)
- Create a new tracking connection with the new “origin/main” 
branch (git branch -u origin/main)
- All local branches should still point to the same commit as base 
revision. If there is a problem (git checkout  && git 
rebase main)

4. Update the integrated systems with CloudStack repos, mainly Travis CI 
and Jenkins configuration with 'main' branch. Check and update UI building, 
apidocs, systemvmtemplate builds; project website and docs (cwiki); and any 
other build/release jobs. Track them through the issue: 
https://github.com/apache/cloudstack/issues/4887.

5. Perform Health Checks (using a dummy PR), and ensure there are no issues 
with the build/release configuration. This PR needs to run full matrix of 
tests. Fix the issues noticed during the health checks.

6. Announce the default branch change to 'main' (and 'master' deprecation) 
on the mailing list.

The vote will be open until Fri 7th May 2021.

For sanity in tallying the vote, Can PMC members please be sure to indicate 
“(binding)” with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

[1] https://markmail.org/message/k767evgjnmzogyhf
[2] https://github.com/github/renaming
[3] 
https://docs.github.com/en/github/administering-a-repository/renaming-a-branch
[4] 
https://docs.github.com/en/github/administering-a-repository/changing-the-default-branch

Regards,
Suresh

Congratulations to Sven - Apache Software Foundation Member

[Paul Angus]

Hi All,

 

More great news.

 

Please join me in congratulating Sven,  for being made a Member of the
Apache Software Foundation. 

 

Congratulations Sven, keep up the good work!

 

Kind regards

 

Paul Angus

 

Congratulations to Gabriel - CloudStack PMC Chair

[Paul Angus]

Hi All CloudStack enthusiasts!

 

Please join me in congratulating Gabriel for becoming the next CloudStack
PMC Chair.

Congratulations Gabriel, very well deserved!

 

I would also like to thank Sven for his great work of the past year!

 

 

 

Kind regards

 

Paul Angus

 

RE: New Joiner

[Paul Angus]

Hi Hoang,

Welcome to the CloudStack community. Glad to have you aboard!

A small point of order, there is no CloudStack Primate project, only the 
CloudStack project.  In fact, what was known as Primate, this is now just 
CloudStack's UI, an integral part of CloudStack.  We are very keen to keep 
CloudStack as a 'turnkey' solution, where a user wouldn't have to do install 
multiple CloudStack 'products' in order to use CloudStack.

That said, any contribution to any part of CloudStack, is extremely welcome. 
Thank you.

Kind regards,


Paul


paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Unitech Mai Nguyen  
Sent: 04 November 2020 02:32
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Cc: sven.vo...@qform.de
Subject: New Joiner

Hello Everyone,

My name is Hoang and I'm currently working for Ewerk.
It is my great pleasure to have a chance to join the Cloudstack Primate project.
It has been a wonderful time for me since last December when I started my first 
task.

I would look forward to being a part of this team for a long time to go. And I 
hope to have your kind help.
Thank you so much.
__
Hoang Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
www.ewerk.xn--com-zq0a

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

__

Unitech Mai Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P
F +49 341 42649 - 98
hoang.ngu...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065

Support:
+49 341 42649 555

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

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.

[ANNOUNCE] Code freeze for 4.15

[Paul Angus]

Hi fellow CloudStackateers,



I'd like to announce a feature code for CloudStack and CloudStack Primate.

We'll go through a period testing  (and only bug fix merges) to get us to
an RC state for both. Then vote on both at the same time (more or less).



Could I ask everyone to have a look at open PRs and issues and help out
with reviews and fixes.



The new UI (Primate) goes GA with this release.  It was a huge endeavour,
so the odd niggle is to be expected,  so please remember to conduct your
manual testing using the new UI and report any bugs.


Many thanks


Paul Angus

[ANNOUNCE] Code freeze for 4.15

[Paul Angus]

Hi fellow CloudStackateers,



I'd like to announce a feature code for CloudStack and CloudStack Primate.

We'll go through a period testing  (and only bug fix merges) to get us to
an RC state for both. Then vote on both at the same time (more or less).



Could I ask everyone to have a look at open PRs and issues and help out
with reviews and fixes.



The new UI (Primate) goes GA with this release.  It was a huge endeavour,
so the odd niggle is to be expected,  so please remember to conduct your
manual testing using the new UI and report any bugs.


Many thanks


Paul Angus

[ANNOUNCE} 4.15 Code Freeze

[Paul Angus]

Hi Everyone,

I hope that you are all coping with the weird world that we are in at the
moment.  And my best wishes to anyone and everyone and hope that we can all
get together at a collab again soon.

I emailed a few months ago to make sure that there were no problems with
having a code freeze in preparation for a new release.  So I'd like to
follow up to say that I'd like to put the code freeze in place at the *end
of next week*, and start the process of ensuring that the master branch is
stable.

I'd like to request that everyone start giving a thought to testing too.
There is a major vSphere refactor to enable a lot of new features which will
need as many scenarios at it as we can, and also we promised the world a GA
Primate.  I understand that there are very few (if any) open bugs for
Primate, but let's try to make sure that we've covered as much as possible.

So, the summary
---

- Code freeze at the end of next week.

- Get ready for testing, and when testing please only use Primate.


Many thanks

Paul Angus

[PROPOSE] Code freeze for 4.15

[Paul Angus]

Hi all,

 

Its around that time of year again.  We owe the world a GA version of
Primate + there is support for Ubuntu 20.04, CentOS 8 and XenServer/XCP-ng
8, a massive update to the vSphere capabilities and many fixes..

 

So, I'd like to propose a feature freeze in two or three weeks' time
(depending how everyone else is looking with any features).  For people who
are a still way out with anything that they're working on; I'd hope to get
back on track with the next release *early* in the new year.

 

Unless there are any objections, I'll go ahead with getting a freeze date
out sooner rather than later.

 

Kind regards

 

 

Paul Angus

 

RE: Error Create VM 4.13.1

[Paul Angus]

This is the error:

2020-06-24 17:26:03,566 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-35:ctx-620bd39c job-211/job-212 ctx-1cf4ef5a) 
(logid:1ee79ed4) Unable to start VM on Host[-6-Routing] 
due to XML error: Non-empty feature list specified without CPU model

what that means I'm afraid I don’t know.  Do you know if you've added something 
to the defaults?


paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: marcos  
Sent: 24 June 2020 21:32
To: users@cloudstack.apache.org
Subject: Error Create VM 4.13.1


When I try to create a VM I am getting the error according to the LOGs below.
I have resources left on the KVM server
SSVMs working perfectly
Computational offer - Local
Disco Offer - Location

Can anyone save me?


2020-06-24 17:26:03,557 DEBUG [c.c.a.t.Request] (AgentManager-Handler-11:null) 
(logid:) Seq 6-5149866173898163465: Processing:  { Ans: , MgmtId: 
8796761733588, via: 6, Ver: v1, Flags: 10, 
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":31,"name":"i-2-31-VM","state":"Starting","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
 7.2","platformEmulator":"CentOS 
7.2","bootArgs":"","enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"yR6FxxzHBSibiwQcMQQOcA","vncAddr":"172.26.0.222","params":{"deployvm":"true"},"uuid":"76edbaeb-6a45-405b-a932-961e12e98cc3","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"5a49cd33-0581-405c-8aa0-dd76193cec94","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fdf04200-8e76-4fd6-9045-18c1f7b8924a","id":2,"poolType":"Filesystem","host":"172.26.0.222","path":"/var/lib/libvirt/images","port":0,"url":"Filesystem://172.26.0.222/var/lib/libvirt/images/?ROLE=Primary=fdf04200-8e76-4fd6-9045-18c1f7b8924a","isManaged":false}},"name":"ROOT-31","size":5368709120,"path":"5a49cd33-0581-405c-8aa0-dd76193cec94","volumeId":33,"vmName":"i-2-31-VM","accountId":2,"format":"QCOW2","provisioningType":"THIN","id":33,"deviceId":0,"bytesReadRate":0,"bytesWriteRate":0,"iopsReadRate":0,"iopsWriteRate":0,"hypervisorType":"KVM"}},"diskSeq":0,"path":"5a49cd33-0581-405c-8aa0-dd76193cec94","type":"ROOT","_details":{"storageHost":"172.26.0.222","managed":"false","storagePort":"0","volumeSize":"5368709120"}},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"path":"template/tmpl/2/204/204-2-1e647bf1-04d0-3541-a0ab-dc27bde551c0.iso","origUrl":"http://mirror.ufam.edu.br/centos/7.8.2003/isos/x86_64/CentOS-7-x86_64-Minimal-2003.iso","uuid":"b0b0c779-43d0-40a7-a31f-33bceb91250b","id":204,"format":"ISO","accountId":2,"checksum":"{SHA-512}c56aba0a569ef605118c642a03529206befac3a5baca329bdf27d1e5578e036dc93952e9ea602897bfb72ded66991f57cea258aa90f12665cde92770c135373a","hvm":true,"displayText":"Centos7Minimal","imageDataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://172.26.0.222/export/secondary","_role":"Image"}},"name":"204-2-1e647bf1-04d0-3541-a0ab-dc27bde551c0","guestOsType":"CentOS
 
7.2","size":1085276160,"hypervisorType":"None","bootable":false,"uniqueName":"204-2-1e647bf1-04d0-3541-a0ab-dc27bde551c0","directDownload":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"pxeDisable":false,"nicUuid":"13df0849-9c60-4def-b124-0a4485629ba1","details":{"ForgedTransmits":"true","PromiscuousMode":"false","MacAddressChanges":"true"},"dpdkEnabled":false,"uuid":"ae49270a-9617-4a07-ae61-72aa58dfec69","ip":"10.1.3.134","netmask":"255.255.255.0","gateway":"10.1.3.1","mac":"02:00:05:76:00:08","dns1":"172.26.0.1","dns2":"","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://571","isolationUri":"vlan://571","isSecurityGroupEnabled":false,"name":"cloudbr1"}],"guestOsDetails":{},"extraConfig":{}},"result":false,"details":"XML
 error: Non-empty feature list specified without CPU model","wait":0}}] }
2020-06-24 17:26:03,558 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-35:ctx-620bd39c job-211/job-212 ctx-1cf4ef5a) 
(logid:1ee79ed4) Seq 6-5149866173898163465: Received:  { Ans: , MgmtId: 
8796761733588, via: 6(kvm-lab-01), Ver: v1, Flags: 10, { StartAnswer } }
2020-06-24 17:26:03,566 INFO  [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-35:ctx-620bd39c job-211/job-212 ctx-1cf4ef5a) 
(logid:1ee79ed4) Unable to start VM on Host[-6-Routing] due to XML error: 
Non-empty feature list specified without CPU model
2020-06-24 17:26:03,575 DEBUG [c.c.v.VirtualMachineManagerImpl] 
(Work-Job-Executor-35:ctx-620bd39c job-211/job-212 ctx-1cf4ef5a) 
(logid:1ee79ed4) Cleaning up resources for the vm VM[User|i-2-31-VM] in 
Starting state
2020-06-24 17:26:03,579 DEBUG [c.c.a.t.Request] 
(Work-Job-Executor-35:ctx-620bd39c job-211/job-212 ctx-1cf4ef5a) 
(logid:1ee79ed4) Seq 6-5149866173898163466: Sending  { Cmd , MgmtId: 
8796761733588, via: 6(kvm-lab-01), Ver: v1, 

RE: [DISCUSS] New default template

[Paul Angus]

My 2 cents:

The default template is not there for general or even production use, it’s 
there for people to 'kick the tires' and either see if CloudStack is what they 
want or check that their installation is generally OK.

Therefore (IMO) the pre-requisites are:

- small download size
- compatibility across all of our supported hypervisors
- compatibility with all CloudStack features; i.e. live memory and CPU 
addition, hot disk-pluging, live migrations which require hypervisor tools 
installed, passing of user-data, meta-data, ssh keys and password resets to the 
VM via VR and config-drive.
- OS commands that users will be relatively familiar with.
- ability to be leverage by Marvin tests to perform smoke and integration tests

You know - the usual stuff...

So that we know that the template should 'always work', I don't think that we 
should point to an upstream repo, but take an OS version, add/configure 
whatever is strictly required to meet our requirements, and keep in the 
CloudStack downloads.

Ok, so more like $10 ..

Kind regards

Paul Angus


paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Andrija Panic  
Sent: 03 June 2020 13:03
To: users 
Cc: dev ; Abhishek Kumar 

Subject: Re: [DISCUSS] New default template

Whatever is a choosen as the new one, needs to be compatible with ALL the 
current hypervisor we support (i. e. VMware 6.0 and up, XenServer 7.0 and up 
and KVM of various flavours).
So that needs to be taken into consideration when speaking about exotic OS-es 
or even the newest ones (Ubuntu 20/CentOS 8) to find a proper OS mappings on 
hypervisor side that will allow it to run normally.



On Wed, 3 Jun 2020, 12:21 ,  wrote:

> Hi,
>
> I'd like to restate my previous stance on this which is - if not to 
> have a proper "market place" of trusted and tested templates - at 
> least to cover the popular ones.
> The basics imho would be CentOS and Ubuntu, with this we cover 99% of 
> the user requirements.
> I'd propose to go with the latest and greatest of both, Ubuntu 20.04 
> and
> CentOS8 respectively (supported 2029).
> I can repurpose the current build machine for openvm.eu and "donate" 
> it to the project so it's not a "third party" any more.
>
> my 2 pence
>
> On 2020-06-03 08:58, Abhishek Kumar wrote:
> > Hi all,
> >
> > I would like to hear everyone's opinion on a new default template in 
> > CloudStack.
> > Currently, we are using CentOS 5.x for different hypervisors but it 
> > is quite old(already completed its support life) and either the 
> > support for it has been removed
> > (https://github.com/xcp-ng/xcp/wiki/Guest-System-Support) or in 
> > legacy (
> https://www.vmware.com/resources/compatibility/search.php?deviceCatego
> ry=software=1=272=448=1_interval
> =10=Partner=Asc=16
> )
> > in different hypervisors.
> > Therefore, I think it is time now to move to a newer OS template. In 
> > my understanding CentOS7 is the minimum viable choice if we are 
> > continuing with CentOS. This can be the preferred choice as we 
> > already have tested templates for it on different hypervisors and it 
> > has 4 years left in its cycle.
> >
> > We can also explore Ubuntu’s cloud-images of 20.04. And if we want 
> > to go with something very light-weight we can think about something 
> > like Alpine Linux.
> >
> > Please have your say. Also, do you think this can be included in 
> > 4.15 itself so we can have a proper default template for something 
> > like XCP-ng 8.x which doesn't support CentOS 5 (and PV VMs)?
> >
> > Regards,
> > Abhishek
> >
> >
> > abhishek.ku...@shapeblue.com
> > www.shapeblue.com
> > 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK 
> > @shapeblue
>

RE: [VOTE] Apache CloudStack 4.14.0.0 RC3

[Paul Angus]

Hi Wesley,

What do you mean by a ' deployment solution' exactly?
In general, there are so many combinations and permutations of use cases + 
network configurations and storage vendors/configurations, 'one-size' generally 
fits nobody.

However, a combination of a bit of Googling and this list will certainly give 
you enough information and help to get you started figuring out the details of 
what's going to work for you.

Kind regards

Paul

paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Wesley Peng  
Sent: 04 June 2020 01:29
To: users@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.14.0.0 RC3

Andrija Panic wrote:
> http://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-
> 4.13.html#time-zone-requirements
> 
> 
> handled in the Upgrade docs - exactly the same..


[OT] is there a cloudstack private IAAS deployment solution? not that large 
scale, most for storage. if there is the commercial solution, we can pay for it.

Thanks.

RE: cloudstack-management fails: com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the database

[Paul Angus]

Hi Eric,

This sounds like you had a failed install/upgrade and then tried again.  The 
second time, CloudStack came to adding a column ('size'), but found that it was 
already there and stopped.


paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Practical XenServer  
Sent: 05 June 2020 05:43
To: users@cloudstack.apache.org
Subject: Re: cloudstack-management fails: 
com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the database

*In one about "Unable to upgrade the database" message on the list*:
Someone else had inquired about whether or not mysql-connector-python had been 
installed. I found that it was installed as a dependency while installing the 
cloudstack-management package...

[root@san-1 ~]# yum list installed | grep 'cloud\|mysql'
cloudstack-common.x86_64   4.14.0.0-1.el7
 @cloudstack
cloudstack-management.x86_64   4.14.0.0-1.el7
 @cloudstack
mysql-connector-python.x86_64  8.0.20-1.el7
 @mysql-connectors-community
mysql-connector-python-cext.x86_64 8.0.20-1.el7  @mysql-connectors-community
mysql80-community-release.noarch   el7-3
installed

*In another message about "*Unable to upgrade the database*" on the list*:
One person recommended completely removing the database and creating it anew.

So I dropped the CloudStack database and re-created it using the 
/usr/bin/cloudstack-setup-databases tool:

/usr/bin/cloudstack-setup-databases cloudstack:#@localhost 
--deploy-as=root:#

And, *at least initially*, this seems to have repaired the situation.

I will update the list with my efforts to add a host *once I'm able to 
install/configure an agent reliably*.

Eric P.
Portland, Oregon

On Fri, Jun 5, 2020 at 5:05 AM Practical XenServer < 
practicalxenser...@gmail.com> wrote:

> After successfully installing and starting Version 4.14 of the 
> Management server on a *fresh* installation of CentOS-7: The 
> management server halts after accessing the WWW interface for the first 
> time...
>
> 2020-06-05 03:30:20,067 ERROR [c.c.u.d.ScriptRunner] (main:null) 
> (logid:) Error executing: alter table vm_template add size bigint 
> unsigned
> 2020-06-05 03:30:20,068 ERROR [c.c.u.d.ScriptRunner] (main:null) 
> (logid:)
> java.sql.SQLSyntaxErrorException: Duplicate column name 'size'
> 2020-06-05 03:30:20,070 ERROR [c.c.u.DatabaseUpgradeChecker] 
> (main:null)
> (logid:) Unable to execute upgrade script
> java.sql.SQLSyntaxErrorException: Duplicate column name 'size'
> ...SNIP...
> Caused by: java.sql.SQLSyntaxErrorException: Duplicate column name 'size'
> ...SNIP...
> ... 50 more
> 2020-06-05 03:30:20,099 DEBUG [c.c.u.d.T.Transaction] (main:null) 
> (logid:) Rolling back the transaction: Time = 35 Name =  Upgrade; 
> called by
> -TransactionLegacy.rollback:890-TransactionLegacy.removeUpTo:833-Trans
> actionLegacy.close:657-DatabaseUpgradeChecker.upgrade:271-DatabaseUpgr
> adeChecker.check:340-CloudStackExtendedLifeCycle.checkIntegrity:65-Clo
> udStackExtendedLifeCycle.start:55-DefaultLifecycleProcessor.doStart:18
> 2-DefaultLifecycleProcessor.access$200:53-DefaultLifecycleProcessor$Li
> fecycleGroup.start:360-DefaultLifecycleProcessor.startBeans:158-Defaul
> tLifecycleProcessor.onRefresh:122
> 2020-06-05 03:30:20,100 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> (main:null) (logid:) Exception encountered during context 
> initialization - cancelling refresh attempt:
> org.springframework.context.ApplicationContextException: Failed to 
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the 
> database
> 2020-06-05 03:30:20,102 WARN  [o.e.j.w.WebAppContext] (main:null) 
> (logid:) Failed startup of context o.e.j.w.WebAppContext@d23e042 
> {/client,file:///usr/share/cloudstack-management/webapp/,UNAVAILABLE}{
> /usr/share/cloudstack-management/webapp}
> org.springframework.context.ApplicationContextException: Failed to 
> start bean 'cloudStackLifeCycle'; nested exception is
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the 
> database ...SNIP...
> Caused by: java.sql.SQLSyntaxErrorException: Duplicate column name 'size'
> ...SNIP...
> ... 50 more
> 2020-06-05 03:30:20,099 DEBUG [c.c.u.d.T.Transaction] (main:null) 
> (logid:) Rolling back the transaction: Time = 35 Name =  Upgrade; 
> called by
> -TransactionLegacy.rollback:890-TransactionLegacy.removeUpTo:833-Trans
> actionLegacy.close:657-DatabaseUpgradeChecker.upgrade:271-DatabaseUpgr
> adeChecker.check:340-CloudStackExtendedLifeCycle.checkIntegrity:65-Clo
> udStackExtendedLifeCycle.start:55-DefaultLifecycleProcessor.doStart:18
> 2-DefaultLifecycleProcessor.access$200:53-DefaultLifecycleProcessor$Li
> fecycleGroup.start:360-DefaultLifecycleProcessor.startBeans:158-Defaul
> tLifecycleProcessor.onRefresh:122
> 2020-06-05 03:30:20,100 WARN  [o.a.c.s.m.c.ResourceApplicationContext]
> 

RE: [DISCUSS] Primate - publishing release and docs

[Paul Angus]

With a bit of - TL;DR ...
And as per Rohit's scope, I'm hand-waving over the formal release process and 
cycle for now.

From our by-laws [1], Non-technical decisions don’t require a vote (I don’t 
agree the rule, but it is what it is); so as no one has disagreed with the idea 
of skipping an RC vote for a tech preview of Primate, I think that’s we can go 
ahead with that unless someone does pop up with an objection.

I would suggest that we don't have call iterations of the tech preview 'RCs'. 
The tech preview is not a 'Release', as that _would_ require a vote, so to have 
release candidates would confuse the issue.  

Wrt documentation, as this is a tech preview, I think that we should limit 
ourselves to the bare minimum to get Primate up and running.  The project has a 
readme for those looking to develop Primate already.  
I think that we need a BIG disclaimer/health warning at the start, instructions 
to download and 'install' and we can trawl github for open issues to give a 
'point-in-time' list of known issues (similar to what we do for PRs in the 
CloudStack releases).  

My 10c would be to simply:  agree when the preview is ready, build the static 
pages, create a tarball and put that on downloads.cloudstack.org .
The instructions are then download, unpack, and place in 
/usr/share/cloudstack-management/webapp/Primate ...

...super simple.

Regards


Paul.



[1] http://cloudstack.apache.org/bylaws.html section 3.4.2

paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Sven Vogel  
Sent: 11 May 2020 10:04
To: users@cloudstack.apache.org
Cc: dev 
Subject: Re: [DISCUSS] Primate - publishing release and docs

Hi Rohit, Hi Daan,

 1.  Documentation for tech preview

I agree with Rohit. For me the both suggestions with links sound like a good 
idea. We should add the download links for official releases or installations 
for each method on both sites. Maybe its a good idea to have both in sync to we 
save us the double work. How can we get them in sync? An important point is 
always the double work. So if there is a method to get them fast in sync in see 
no problem but if there is many hand work to do maybe its easier to refer from 
wiki -> to readthedocs or vice versa. I would like to prevent outdated docs on 
one place.

@Daan
I think Primate should be documented by means of help pop-ups with links to the 
underlaying API and admin docs. How big do you expect this documentation to 
become? (I would think it is only a short readme on first
use)

— How could this work? Where we could find the help pop-ups and where should 
they located?



 2.  Types of Primate packages:

*   deb/rpm: Primate already supports deb/rpm packages. This mode will allow 
users to install "cloudstack-primate" on the management server where Primate 
will be served from the management server just like the old UI.
*   docker container: Primate support docker containers to be built/used which 
takes a nginx config to proxy /client path to any management server.
*   archive build: A built archive (tar.gz) of Primate can be extracted and 
allow users/admins to do any custom hosting with it, other than (a) or (b).

— For me all three methods are a good idea because we give the user the 
greatest flexibility.

a) a repository for rpm and deb
b) publish a docker like ready to use version always dockerhub. By the way 
everybody can build there own docker container

c) publish the tar.gz on the release section in GitHub or as tar.gz on 
repository too? What do you think @Rohit, @Daan?



 3.  Hosting packages/releases

*   Use download.cloudstack.org for hosting (a) 
deb/rpm repos, and (c) archive builds.

— sounds good to me. I would prefer this place.

*   Use the apache dockerhub org to publish official Primate container images: 
https://hub.docker.com/r/apache/cloudstack-primate

— sounds good to me. I would prefer docker hub

My suggestion is to host the tar.gz as release with tags on GitHub, but I am 
open to put it on the repsository too. Its depend on the work we have and maybe 
its better to have rpm, deb or

So I thinks this is good because we have three good understandable places. Most 
people look for a repository for rpm/deb, docker on dockerhub and code release 
(tar.gz) on GitHub.

[ANNOUNCE] Next PMC Chair & VP Apache CloudStack Project - Sven Vogel

[Paul Angus]

Hi Everyone,

It gives me great pleasure to announce that ASF board last night
accepted our PMC's nomination of Sven Vogel as the next VP of the
project.

As I hand over the reins, I would like to thank everyone for the
support I've received over the past year. It looks like being a very
difficult year ahead for the world in general, and I wish everyone
good luck in navigating it and urge everyone to try to show patience
and compassion in these trying times.

I'd like to thank Sven for volunteering for the post and wish him the
best of luck, I'm sure that he'll do a great job.

So please join me in welcoming Sven Vogel as the new Apache CloudStack
VP and PMC Chair !

RE: [DISCUSS] Honouring listall=true in API calls to include project resources

[Paul Angus]

Ideally, yes.  The use case for 'listall' for the Admin including networks in 
projects, is pretty much the same as for Admins wanting to see VMs and VRs in 
projects... 

It's hard to manage something that you can't see... ☹



paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav  
Sent: 19 February 2020 09:51
To: Paul Angus ; users@cloudstack.apache.org; 
d...@cloudstack.apache.org
Subject: Re: [DISCUSS] Honouring listall=true in API calls to include project 
resources

Yes Paul, I've tested for routers and ilbvms - you can test yourself here:

http://primate-qa.cloudstack.cloud:8080/client/master/ (or using cmk)

I just checks, won't work for networks - you want me to fix that?


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com


From: Paul Angus 
Sent: Wednesday, February 19, 2020 15:02
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Subject: RE: [DISCUSS] Honouring listall=true in API calls to include project 
resources

Does this include networks and VRs?

It's a real pain not being able to see them all..

paul.an...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK @shapeblue




rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK @shapeblue
  
 


-Original Message-
From: Rohit Yadav 
Sent: 19 February 2020 08:42
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: [DISCUSS] Honouring listall=true in API calls to include project 
resources

All,

Many list APIs, such as the listRouters API, accept a `listall` parameter as 
well as a `projectid` parameter. Currently, on calling a list API with 
listall=true and projectid=-1 it only returns resources belonging to all 
projects, the listall=true parameter is effectively ignored.

We've come up with a PR that fixes the list APIs (mainly for Primate) to return 
all the resources including project when both listall=true and projectid=-1 are 
passed, by a non-normal user (i.e. the admin and domain-admin user):

https://github.com/apache/cloudstack/pull/3894/files (the PR also fixed 
incorrect use in old UI)


This will fix the multiple-api calling hack and Primate would be able to say 
list all routers in Infra->Routers with a single API call.

In current UI, for example, to see all the routers under Infra -> Routers, two 
API calls are made with and without projectid=-1. The code in fact ignores the 
listall=true when projectid=-1 is used.


However, this may break "soft" compatibility when both 
listall=true=-1 are passed for some list APIs, as:

  *   Old behaviour: will only returns resources belonging to a project, only 
to admin and domain admin
  *   New behaviour: will return all resources including project resources, 
only to admin and domain admin
  *   Additional notes: normal user (not an admin, or a domain admin etc) will 
not be affected

The listall parameter is documented as "if set to true - list resources that 
the caller is authorized to see", PR intends to fix this behaviour bug.

As far as I can tell the projectid=-1 is only used in the current UI, any 
users, dev want to share their concerns, thoughts?

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK @shapeblue

RE: [DISCUSS] Honouring listall=true in API calls to include project resources

[Paul Angus]

Does this include networks and VRs?

It's a real pain not being able to see them all..

paul.an...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 


-Original Message-
From: Rohit Yadav  
Sent: 19 February 2020 08:42
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: [DISCUSS] Honouring listall=true in API calls to include project 
resources

All,

Many list APIs, such as the listRouters API, accept a `listall` parameter as 
well as a `projectid` parameter. Currently, on calling a list API with 
listall=true and projectid=-1 it only returns resources belonging to all 
projects, the listall=true parameter is effectively ignored.

We've come up with a PR that fixes the list APIs (mainly for Primate) to return 
all the resources including project when both listall=true and projectid=-1 are 
passed, by a non-normal user (i.e. the admin and domain-admin user):

https://github.com/apache/cloudstack/pull/3894/files (the PR also fixed 
incorrect use in old UI)


This will fix the multiple-api calling hack and Primate would be able to say 
list all routers in Infra->Routers with a single API call.

In current UI, for example, to see all the routers under Infra -> Routers, two 
API calls are made with and without projectid=-1. The code in fact ignores the 
listall=true when projectid=-1 is used.


However, this may break "soft" compatibility when both 
listall=true=-1 are passed for some list APIs, as:

  *   Old behaviour: will only returns resources belonging to a project, only 
to admin and domain admin
  *   New behaviour: will return all resources including project resources, 
only to admin and domain admin
  *   Additional notes: normal user (not an admin, or a domain admin etc) will 
not be affected

The listall parameter is documented as "if set to true - list resources that 
the caller is authorized to see", PR intends to fix this behaviour bug.

As far as I can tell the projectid=-1 is only used in the current UI, any 
users, dev want to share their concerns, thoughts?

Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK @shapeblue
  
 

RE: Security Groups default behavior

[Paul Angus]

Hi Florent,

No, two VMs in the same security group will have the same rules applied to 
them.  So if they both allow outbound port 22, they won't be able to talk over 
SSH, as neither allows inbound SSH.

If your network was created with a default allow, then they will be able to 
communicate over all ports until you start applying rules to them.

Paul.

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


-Original Message-
From: Florent Paillot  
Sent: 04 November 2019 16:01
To: cs users 
Subject: Security Groups default behavior

Hello, 
I'm looking for the default behavior for Security Groups when using a shared 
network with SG support. Can't find it in the docs. 
Are two VM in the same SG implicitly allowed to communicate with each other ? 

Maybe i'm wrong but it's seemed to be the case with 4.9.3 (KVM) but not anymore 
with 4.11.3 (KVM). 

Thanks 

RE: [DISCUSS] CloudStack Kubernetes Service plugin

[Paul Angus]

Hi Sven,

The cloudstack-kubernetes-provider is a plugin for Kubernetes which enables 
Kubernetes to drive CloudStack actions, such as opening firewall ports.
The CloudStack Kubernetes service, enables end users to request say, a 
Kubernetes cluster with 1 master and 4 workers (based on a user requested 
service offering).  CloudStack takes care of the plumbing and configuration to 
get the base cluster operational.


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


-Original Message-
From: Sven Vogel  
Sent: 25 September 2019 19:18
To: dev 
Cc: users@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin

Sounds interesting.

For me there are also some questions like Pierre.

If I understand it correctly all nodes inclusive the masters will be deployed 
from a core os template?
What are the pvc or storage class backend which are available to the cluster 
nodes? (Local storage from the core os vms?)

And now a little bit sorting… what’s the difference between… its a little 
confusing ...

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service
or
https://github.com/apache/cloudstack-kubernetes-provider

Cheers

Sven


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog<https://blog.ewerk.com/> | 
LinkedIn<https://www.linkedin.com/company/ewerk-group> | 
Xing<https://www.xing.com/company/ewerk> | 
Twitter<https://twitter.com/EWERK_Group> | 
Facebook<https://de-de.facebook.com/EWERK.IT/>

Mit Handelsregistereintragung vom 09.07.2019 ist die EWERK RZ GmbH auf die 
EWERK IT GmbH verschmolzen und firmiert nun gemeinsam unter dem Namen: EWERK 
DIGITAL GmbH, für weitere Informationen klicken Sie 
hier<https://www.ewerk.com/ewerkdigital>.

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 25.09.2019 um 19:29 schrieb Paul Angus 
mailto:paul.an...@shapeblue.com>>:

The FS is here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service

I'll let Abhishek fill in any gaps between whats in the FS and your questions - 
it might be good to comment on the FS so all of this gets captured.
The one thing I would add is that we see this as just the next iteration of the 
feature, not the end goal.  So we would look to add functionality after it goes 
live, but we would also welcome any others wishing to extend the functionality 
too...

Kind regards
Paul.



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




-Original Message-
From: Pierre-Luc Dion 
Sent: 25 September 2019 18:12
To: d...@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin

Make sense for the proposed implementation, would it handle redundant master?
How would the k8s cluster would be created, using Rancher tools, kubectl or 
other?

so far, the small part I understand from MaaS, it could be very interesting to 
integrate it to cloudstack in a way where it could be use to  scale Hypervisor 
host, specially KVM nodes.


On Wed, Sep 25, 2019 at 10:47 AM Paul Angus 
wrote:

The proposed implementation will create a master and n worker nodes.
It will also support (graceful) cluster resizing, the next step would be to 
enable the CloudStack plugin for Kubernetes to allow Kubernetes to drive that 
scaling, so that you can scale with demand rather than needing to oversize you 
environment to begin with.

I've been keeping MaaS in mind as way of doing baremetal Kubernetes along side 
VM based Kubernetes clusters.  Interestingly a few people that I have spoken to 
have said that they prefer the use of VMs, because whole servers as the unit of 
scale is often very wasteful, unless you 'share' them whi

RE: [DISCUSS] CloudStack Kubernetes Service plugin

[Paul Angus]

The FS is here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Kubernetes+Service

I'll let Abhishek fill in any gaps between whats in the FS and your questions - 
it might be good to comment on the FS so all of this gets captured.
The one thing I would add is that we see this as just the next iteration of the 
feature, not the end goal.  So we would look to add functionality after it goes 
live, but we would also welcome any others wishing to extend the functionality 
too...

Kind regards
Paul.



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


-Original Message-
From: Pierre-Luc Dion  
Sent: 25 September 2019 18:12
To: d...@cloudstack.apache.org
Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin

Make sense for the proposed implementation, would it handle redundant master?
How would the k8s cluster would be created, using Rancher tools, kubectl or 
other?

so far, the small part I understand from MaaS, it could be very interesting to 
integrate it to cloudstack in a way where it could be use to  scale Hypervisor 
host, specially KVM nodes.


On Wed, Sep 25, 2019 at 10:47 AM Paul Angus 
wrote:

> The proposed implementation will create a master and n worker nodes.
> It will also support (graceful) cluster resizing, the next step would 
> be to enable the CloudStack plugin for Kubernetes to allow Kubernetes 
> to drive that scaling, so that you can scale with demand rather than 
> needing to oversize you environment to begin with.
>
> I've been keeping MaaS in mind as way of doing baremetal Kubernetes 
> along side VM based Kubernetes clusters.  Interestingly a few people 
> that I have spoken to have said that they prefer the use of VMs, 
> because whole servers as the unit of scale is often very wasteful, 
> unless you 'share' them which has all sorts of security implications...
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Pierre-Luc Dion 
> Sent: 25 September 2019 15:31
> To: d...@cloudstack.apache.org
> Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
>
> Hi Paul,
>
> Yeah, was bad timing for the CCCNA this year unfortunately :-(,  I'm not
> sure I'm curious to see how cloudstack could become more "other Apache
> products friendly" but I don't have particular use case compared to k8s
> integration. Has you are suggesting, would probably make sense to use Helm
> to deploy any other application stack.
>
> btw, we are still working on the Canonical MaaS integration, a bit more
> challenging than anticipated...
>
>
> To get back to a *Kubernetes Service plugin*:
> To me, as a user of cloudstack at the moment, If I deploy a k8s cluster, I
> need to deploy monstrous instances for worker nodes.
> which doesn't make sense if I'm a cloud consumer. So I think we need to
> solve something challenging: a k8s service that would scale has needed
> while keeping in mind redundancy of worker nodes without sacrifice on
> security. Is the worker node is part of the ongoing work or it's more about
> offering a k8s master and api infrastructure to a user ?
>
> An easy path would be some kind of shared worker nodes pool but that
> involve possible security risk unless you would trust users that consume
> those workers.
>
>
> On Wed, Sep 25, 2019 at 10:15 AM Paul Angus 
> wrote:
>
> > Hi Pierre-Luc,
> >
> > (we missed you at CCCNA!) How are you seeing CloudStack being more
> > deployment friendly?  What you do think that we could do on top of
> > creating the Kubenetes Cluster to begin with?
> > [thinking out loud - we could pre-package Tiller to make it easier to
> > deploy openWhisk via Helm charts ? ]
> >
> > Kind regards
> >
> >
> > Paul.
> >
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Pierre-Luc Dion 
> > Sent: 25 September 2019 13:37
> > To: d...@cloudstack.apache.org
> > Subject: Re: [DISCUSS] CloudStack Kubernetes Service plugin
> >
> > Hi Rohit, Nux,
> >
> > Thanks Rohit for cloudstack-provider, that's exactly it ! :-D Nux, I
> agree
> > with your opinion, but there is a lot of interest for k8s and seams like
> a
> > lot of organisations are moving to container based infrastructures to
> > standardized their deployment.
> >
> > if we want to extent the discussion to function as a service, would you
> > guys see a possibility for us to be more aligned 

[ANNOUNCE] Apache CloudStack 4.13.0.0 GA

[Paul Angus]

*The Apache Software Foundation Announces Apache**®** CloudStack**®** v4.13*


Apache CloudStack v4.13 features nearly 200 new features, enhancements and
fixes since 4.12., such as enhanced hypervisor support, performance
increases and more user-configurable controls.  Highlights include:



   - Supporting configuration of virtualised appliances
   - VMware 6.7 support
   - Increased granularity & control of instance  deployment
   - Improvements in system VM performance
   - Allow live migration of DPDK enabled instances
   - More flexible UI branding
   - Allowing users to create layer 2 network offerings


The full list of new features can be found in the project release notes at
http://docs.cloudstack.apache.org/en/4.13.0.0/releasenotes/changes.html



Apache CloudStack powers numerous elastic Cloud computing services,
including solutions that have ranked as Gartner Magic Quadrant leaders.
Highlighted in the Forrester Q4 2017 Enterprise Open Source Cloud Adoption
report, Apache CloudStack "sits beneath hundreds of service provider
clouds", including Fortune 5 multinational corporations. A list of known
Apache CloudStack users are available at
http://cloudstack.apache.org/users.html

[ANNOUNCE] Apache CloudStack 4.13.0.0 GA

[Paul Angus]

*The Apache Software Foundation Announces Apache**®** CloudStack**®** v4.13*


Apache CloudStack v4.13 features nearly 200 new features, enhancements and
fixes since 4.12., such as enhanced hypervisor support, performance
increases and more user-configurable controls.  Highlights include:



   - Supporting configuration of virtualised appliances
   - VMware 6.7 support
   - Increased granularity & control of instance  deployment
   - Improvements in system VM performance
   - Allow live migration of DPDK enabled instances
   - More flexible UI branding
   - Allowing users to create layer 2 network offerings


The full list of new features can be found in the project release notes at
http://docs.cloudstack.apache.org/en/4.13.0.0/releasenotes/changes.html



Apache CloudStack powers numerous elastic Cloud computing services,
including solutions that have ranked as Gartner Magic Quadrant leaders.
Highlighted in the Forrester Q4 2017 Enterprise Open Source Cloud Adoption
report, Apache CloudStack "sits beneath hundreds of service provider
clouds", including Fortune 5 multinational corporations. A list of known
Apache CloudStack users are available at
http://cloudstack.apache.org/users.html

RE: [DISCUSS] Primate - new UI for CloudStack?

[Paul Angus]

Lol - with great power comes great responsibility David! 

Actually this is a discussion thread, once any issues which people may raise 
are ironed out I expect Rohit will start a VOTE on a concrete proposal and 
timeline.
-- For anyone not used to this process, now would be a good time to explain 
Apache voting rules (https://www.apache.org/foundation/voting.html)

From PMC members on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I object to this change (VETO)

From the rest of the community on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I don't like this change.

As this change would effect so many people, I would hope that any issues would 
be raised during the discussion and a mutually acceptable way forward found, 
before we get as far as a vote.  


Kind regards


Paul Angus





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


-Original Message-
From: David Merrill  
Sent: 20 September 2019 18:27
To: us...@cloudstack.apache.org
Subject: Re: [DISCUSS] Primate - new UI for CloudStack?

I love this idea. Separating the UI from the code-base and crafting an API 
driven UI presents excellent opportunities for customizable UIs (and getting 
folks involved with making them) which can improve user experience.

I'd love to get involved and looking forward to trying it out.

+1 (I've never +1'ed anything before, is it OK? Can I vote?) :)

David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services OTELCO
92 Oak Street, Portland ME 04101
office 207.772.5678  
http://www.otelco.com/cloud-and-managed-services
 
Confidentiality Message
The information contained in this e-mail transmission may be confidential and 
legally privileged. If you are not the intended recipient, you are notified 
that any dissemination, distribution, copying or other use of this information, 
including attachments, is prohibited. If you received this message in error, 
please call me at 207.772.5678  so this error can be 
corrected.
 

On 9/20/19, 12:52 PM, "Simon Weller"  wrote:

I like the idea of separating the UI from the main code base. I think that 
will provide a lot more flexibility moving forward and the project is well 
overdue for a new look and feel.

I think the time frame proposed to sunset the old UI is doable and we'll 
need some feedback from those using it today (we have our own UI, so this 
doesn't affect us).

One of our challenges over the last few years is the added work of getting 
UI features into the release and it has added around 30% additional work load 
due to the older style code of the current UI. Having it in VUE is great and I 
think it will also encourage others to contribute.

+1.


From: Anurag A 
Sent: Friday, September 20, 2019 11:26 AM
To: d...@cloudstack.apache.org 
Cc: us...@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - new UI for CloudStack?

+1 to the new UI as it supports:
1. Faster development of features
2. Better experience as a user
3. Easy customisation declaratively

Regards,
Anurag

> On 20-Sep-2019, at 8:17 AM, Siddhartha Kattoju  
wrote:
>
> +1 from me as well.
>
> Just a side note: I feel like there is a high risk of tldr here. May be 
its
> just me. It may be would be good to put most of the details in a wiki page
> and just post a summarized version on the list ?
>
> *Sid Kattoju*
>
> Cloud Software Architect | Professional Services
>
> c 514.466.0951
>
>
> * <https://goo.gl/NYZ8KK>*
>
>
>
>
> On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
> wrote:
>
>> All,
>>
>>
>>
>> == Summary ==
>>
>>
>> I have been working on a new, modern role-based UI for Cloudstack 
(project
>> Primate: https://github.com/shapeblue/primate) I demoed this for the
>> first time at CCCNA19 last week and it was very well received. It was
>> discussed, at length, as an item in the hackathon and the general 
consensus
>> there was that this could become Cloudstacks new UI. We discussed a plan 
to
>> achieve that and now I’m bringing that plan to the list for discussion.
>>
>>
>>
>> == Background ==
>>
>>
>> The current CloudStack UI has grown technical debt over time and it has
>> become harder to extend, develop, maintain in the long run, it is also
>> difficult for new contributors to learn and get started. Since late 
2018, I
>> started working on a side-project with the aim to create a modern
>> progre

RE: [DISCUSS] Primate - new UI for CloudStack?

[Paul Angus]

Lol - with great power comes great responsibility David! 

Actually this is a discussion thread, once any issues which people may raise 
are ironed out I expect Rohit will start a VOTE on a concrete proposal and 
timeline.
-- For anyone not used to this process, now would be a good time to explain 
Apache voting rules (https://www.apache.org/foundation/voting.html)

From PMC members on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I object to this change (VETO)

From the rest of the community on code changes:
+1 = yes I agree, lets do this
0 = I don't mind/care either way
-1 = I don't like this change.

As this change would effect so many people, I would hope that any issues would 
be raised during the discussion and a mutually acceptable way forward found, 
before we get as far as a vote.  


Kind regards


Paul Angus





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


-Original Message-
From: David Merrill  
Sent: 20 September 2019 18:27
To: users@cloudstack.apache.org
Subject: Re: [DISCUSS] Primate - new UI for CloudStack?

I love this idea. Separating the UI from the code-base and crafting an API 
driven UI presents excellent opportunities for customizable UIs (and getting 
folks involved with making them) which can improve user experience.

I'd love to get involved and looking forward to trying it out.

+1 (I've never +1'ed anything before, is it OK? Can I vote?) :)

David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services OTELCO
92 Oak Street, Portland ME 04101
office 207.772.5678  
http://www.otelco.com/cloud-and-managed-services
 
Confidentiality Message
The information contained in this e-mail transmission may be confidential and 
legally privileged. If you are not the intended recipient, you are notified 
that any dissemination, distribution, copying or other use of this information, 
including attachments, is prohibited. If you received this message in error, 
please call me at 207.772.5678  so this error can be 
corrected.
 

On 9/20/19, 12:52 PM, "Simon Weller"  wrote:

I like the idea of separating the UI from the main code base. I think that 
will provide a lot more flexibility moving forward and the project is well 
overdue for a new look and feel.

I think the time frame proposed to sunset the old UI is doable and we'll 
need some feedback from those using it today (we have our own UI, so this 
doesn't affect us).

One of our challenges over the last few years is the added work of getting 
UI features into the release and it has added around 30% additional work load 
due to the older style code of the current UI. Having it in VUE is great and I 
think it will also encourage others to contribute.

+1.


From: Anurag A 
Sent: Friday, September 20, 2019 11:26 AM
To: d...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: Re: [DISCUSS] Primate - new UI for CloudStack?

+1 to the new UI as it supports:
1. Faster development of features
2. Better experience as a user
3. Easy customisation declaratively

Regards,
Anurag

> On 20-Sep-2019, at 8:17 AM, Siddhartha Kattoju  
wrote:
>
> +1 from me as well.
>
> Just a side note: I feel like there is a high risk of tldr here. May be 
its
> just me. It may be would be good to put most of the details in a wiki page
> and just post a summarized version on the list ?
>
> *Sid Kattoju*
>
> Cloud Software Architect | Professional Services
>
> c 514.466.0951
>
>
> * <https://goo.gl/NYZ8KK>*
>
>
>
>
> On Fri, Sep 20, 2019 at 8:10 AM Rohit Yadav 
> wrote:
>
>> All,
>>
>>
>>
>> == Summary ==
>>
>>
>> I have been working on a new, modern role-based UI for Cloudstack 
(project
>> Primate: https://github.com/shapeblue/primate) I demoed this for the
>> first time at CCCNA19 last week and it was very well received. It was
>> discussed, at length, as an item in the hackathon and the general 
consensus
>> there was that this could become Cloudstacks new UI. We discussed a plan 
to
>> achieve that and now I’m bringing that plan to the list for discussion.
>>
>>
>>
>> == Background ==
>>
>>
>> The current CloudStack UI has grown technical debt over time and it has
>> become harder to extend, develop, maintain in the long run, it is also
>> difficult for new contributors to learn and get started. Since late 
2018, I
>> started working on a side-project with the aim to create a modern
>> progre

Re: Hackathon @apachecon

[Paul Angus]

Hi Sayed,

You're more than welcome the talks will be Monday and Tuesday the Hackathon is 
Wednesday.  You'll need to register via http://us.cloudstackcollab.org/#attend


From: sayed muzammil 
Sent: Saturday, September 7, 2019 4:34:35 PM
To: users@cloudstack.apache.org 
Subject: Re: Hackathon @apachecon

Wish to join conference


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

On Saturday, September 7, 2019, Marcus  wrote:

> I think some direction may come out of what we see at the conference.
>
> UX - UI, API, CLI
> KVM agent communication model
>
> On Friday, September 6, 2019, Paul Angus  wrote:
>
> > Hi All,
> >
> > We have a large room for the day on Wednesday for a hackathon.  I think
> it
> > might be a good idea if we marshal some thoughts around what we'd like to
> > do with the time.
> > I guess that we'll end up with some splinter groups who want to work on
> > something very specific together as well, I can't see that being a
> problem.
> >
> > Some thing that I'd like to put out there as a discussion is the
> > networking models - there has been talk of rationalising and dropping
> > 'basic' networks as a separate model and using advanced networks with
> > security groups instead.  Also the combining of the VR and VPC code to
> make
> > an isolated network a single tier VPC.   I'd like to have a group
> > discussion around what everyone would like to do and how we might do it.
> >
> > Are there any other topics that people think that would benefit from a
> > group discussion ?
> >
> >
> > Cheers
> >
> >
> > Paul Angus
> >
> >
> > paul.an...@shapeblue.com
> > www.shapeblue.com<http://www.shapeblue.com>
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>


--
<https://about.me/desidude03?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>
Sayed Muzammil
about.me/desidude03
<https://about.me/desidude03?promo=email_sig_source=product_medium=email_sig_campaign=gmail_api_content=thumb>

Hackathon @apachecon

[Paul Angus]

Hi All,

We have a large room for the day on Wednesday for a hackathon.  I think it 
might be a good idea if we marshal some thoughts around what we'd like to do 
with the time.
I guess that we'll end up with some splinter groups who want to work on 
something very specific together as well, I can't see that being a problem.

Some thing that I'd like to put out there as a discussion is the networking 
models - there has been talk of rationalising and dropping 'basic' networks as 
a separate model and using advanced networks with security groups instead.  
Also the combining of the VR and VPC code to make an isolated network a single 
tier VPC.   I'd like to have a group discussion around what everyone would like 
to do and how we might do it.

Are there any other topics that people think that would benefit from a group 
discussion ?


Cheers


Paul Angus


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

[VOTE][RESULT] Apache CloudStack 4.13.0.0

[Paul Angus]

Hi all,

After 3 business days, the vote for CloudStack 4.13.0.0 *passes* with 3 PMC
+ 1 non-PMC votes.

+1 (PMC / binding)
* Gabriel Beims Bräscher
* Boris Stoyanov
* Rohit Yadav

+1 (nonbinding)
* Liridon Ismaili

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to give 
the mirrors time to catch up.


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

Re: [VOTE] Apache CloudStack 4.13.0.0 RC2

[Paul Angus]

We're looking good to for a release, but I'm just holding off to hear from 
Gabriel who raised a blocker last time around.

@gabrasc...@gmail.com<mailto:gabrasc...@gmail.com>  are you testing this RC 
(should we wait for you)?


From: Ismaili, Liridon (SWISS TXT) 
Sent: Friday, August 30, 2019 3:54:45 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.13.0.0 RC2

Hi Guys,

+1 from our side

Following upgrade was done:
from 4.11.3 to 4.13 RC2
- VMWare 6.5
- Advanced network setup

Post upgrade steps:
- redeployed systemVMs
- redeployed vRouters

Tests done:
- create / started / stopped / destroyed VMs which were created before and 
after the upgrade
- create / restart / cleanup / redundant vRouters
- upload / delete templates and multi disk templates
- create / delete projects / accounts / users

Regards
Liridon

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


-Original Message-
From: Paul Angus 
mailto:paul%20angus%20%3cpaul.an...@shapeblue.com%3e>>
Reply-To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
To: d...@cloudstack.apache.org 
mailto:%22...@cloudstack.apache.org%22%20%3c...@cloudstack.apache.org%3e>>,
 users@cloudstack.apache.org 
mailto:%22us...@cloudstack.apache.org%22%20%3cus...@cloudstack.apache.org%3e>>
Subject: [VOTE] Apache CloudStack 4.13.0.0 RC2
Date: Wed, 28 Aug 2019 22:02:32 +


Hi All,


We had an excellently low number of bugs in RC1, so here's RC2 with just 3 
fixes...


I've created a 4.13.0.0 release (RC2), with the following artefacts up for 
testing and a vote:


Git Branch and Commit SH:

<https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535>

https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535


Commit: 7c7efe76013675b476d8aa14c36a353cd5d429fc


Source release (checksums and signatures are available at the same location):

<https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/>

https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/



PGP release keys (signed using 51EE0BC8):

<https://dist.apache.org/repos/dist/release/cloudstack/KEYS>

https://dist.apache.org/repos/dist/release/cloudstack/KEYS



The vote will be open until 31st August.


For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?


[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)


Additional information:


For users' convenience, I've built packages from 
7c7efe76013675b476d8aa14c36a353cd5d429fc and published RC1 repository here:

<http://packages.shapeblue.com/testing/41300rc2/>

http://packages.shapeblue.com/testing/41300rc2/



The systemvm templates are unchanged from 4.11.3/4.12.0:

<http://download.cloudstack.org/systemvm/4.11/>

http://download.cloudstack.org/systemvm/4.11/



Fixes in RC2


#3566   server: fix NPE for the case where volume is not attached to a VM

#3567   fix xenserver 7.1.0 os mapping typo

#3571   Unable to deploy VMs via UI in advanced networks with SG and IPv6 cidr





<mailto:paul.an...@shapeblue.com>

paul.an...@shapeblue.com



<http://www.shapeblue.com>

www.shapeblue.com<http://www.shapeblue.com>


Amadeus House, Floral Street, London  WC2E 9DPUK

@shapeblue

[VOTE] Apache CloudStack 4.13.0.0 RC2

[Paul Angus]

Hi All,

We had an excellently low number of bugs in RC1, so here's RC2 with just 3 
fixes...

I've created a 4.13.0.0 release (RC2), with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535
Commit: 7c7efe76013675b476d8aa14c36a353cd5d429fc

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/

PGP release keys (signed using 51EE0BC8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 31st August.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from 
7c7efe76013675b476d8aa14c36a353cd5d429fc and published RC1 repository here:
http://packages.shapeblue.com/testing/41300rc2/

The systemvm templates are unchanged from 4.11.3/4.12.0:
http://download.cloudstack.org/systemvm/4.11/

Fixes in RC2

#3566   server: fix NPE for the case where volume is not attached to a VM
#3567   fix xenserver 7.1.0 os mapping typo
#3571   Unable to deploy VMs via UI in advanced networks with SG and IPv6 cidr




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

RE: inquiry project status

[Paul Angus]

The longer form of the answer is;

Yes there is a lot of development going on, the last release (4.12) was Q2 this 
year, the next release is going through release candidate testing right now.  
The CloudStack Collaboration Conference,  where much of the community gets 
together to talk about what's going on will be in Las Vegas in a few weeks 
co-located with ApacheCon
http://us.cloudstackcollab.org/#attend


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


-Original Message-
From: Andrija Panic  
Sent: 28 August 2019 05:32
To: users 
Subject: Re: inquiry project status

Yes.

On Wed, Aug 28, 2019, 05:12 Cloud Cache  wrote:

> Hello,
>
> Is this project still in active development for cloud integration?
>
> thanks.
>

RE: [DISCUSS] Change of the official CHAT channel

[Paul Angus]

I don't think that we should be 'marketing' anything other than the mailing 
lists.That is where most people can be found and where previously asked 
questions can be searched for.
Having a ready to roll 'chat' tool has many advantages, so I'm cool with having 
one in the back pocket.
But personally I'd like to see as little fragmentation of the community as 
possible.

+ a new visitor turning up to a slack channel with 4 people on it is not going 
to give a positive impression, and that person is definitely is far less likely 
to get an answer to any question that they have.

Paul.

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


-Original Message-
From: Gabriel Beims Bräscher  
Sent: 23 August 2019 14:56
To: dev 
Cc: Nux! 
Subject: Re: [DISCUSS] Change of the official CHAT channel

Hello folks,

I see no problem with using chat platforms. The mail should stay as the default 
communication tool indeed, but several times I used Slack when helping foes 
around, raising questions, and pinging folks on private chat.
As far as we have tools and they are being used by the community I see no 
problem with keeping them around.

However, I think that the main point raised by Andrija is regarding the 
"marketing" of the channels. We normally promote IRC (pointing to 
irc.freenode.net), but CloudStack IRC channels look pretty dead, especially 
considering that it is the "official" ACS chat tool.

Does promoting all channels (IRC + Slack) look a good idea? Should we keep only 
one option? In one hand, IRC currently is not as active as Slack, but on the 
other hand, Slack requires an invitation e-mail.

Regards,
Gabriel.



Em sex, 23 de ago de 2019 às 08:45, Rohit Yadav 
escreveu:

> All,
>
> I think email is the more persistent form of communication and it must 
> continue to be the default communication mechanism for the project
> dev+user+etc.
>
> For a more real-time/transient communication, IRC or slack are good tools.
> I don't have any preference on either, as I'm not an active user on 
> either of them. It just happened that someone asked me to join the-asf 
> slack for some other group, and I saw many projects having their 
> channels there and I made a comment about it on our current 
> apachecloudstack community slack which is outside of the-asf group. 
> I've got both of them setup on my desktop slack now, if it's too 
> difficult to migrate everyone from the old slack group to the-asf 
> slack group, let's continue as is; or perhaps add an IRC-gateway between the 
> two.
>
>
> Regards,
>
> Rohit Yadav
>
> Software Architect, ShapeBlue
>
> https://www.shapeblue.com
>
> 
> From: Sven Vogel 
> Sent: Friday, August 23, 2019 01:01
> To: d...@cloudstack.apache.org 
> Cc: Nux! 
> Subject: Re: [DISCUSS] Change of the official CHAT channel
>
> Hey Guys,
>
> I don’t understand the problem. I don’t like slack too but I don’t 
> like mailing list or  neither. I think the first one is closed and 
> slow. For me is an mailing list or irc also not the wisdom final 
> conclusion but hey do we have a better one? No.
>
> If IRC is death drop it. If we don’t want slack drop it. leave ONLY 
> the mailing list until there we get an better interactive technology, 
> maybe open source.
>
> Cheers
>
>
> __
>
> 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
> 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 22.08.2019 um 20:28 schrieb Andrija Panic :
> >
> > My whole idea is that having one (IRC) marketed on web pages, while 
> > using the other silently (Slack) makes less than zero sense to me.
> >
> > And, for me, a tool is a tool, I'm not married to 

RE: [DISCUSS] Change of the official CHAT channel

[Paul Angus]

Personally, I agree with Nux, I could live without yet another communication 
medium that I have to check. So I would prefer the searchable medium of the 
mailing lists with the fall back of maybe Slack for group calls or chats if 
really required.   Given the worldwide time zones we cover, real-time 
conversations are automatically going to exclude a large number of people.  The 
conversation threading in email clients allows me to see the subject of a 
conversation and decide if can or want to join in.

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


-Original Message-
From: Andrija Panic  
Sent: 22 August 2019 19:28
To: Nux! 
Cc: dev 
Subject: Re: [DISCUSS] Change of the official CHAT channel

My whole idea is that having one (IRC) marketed on web pages, while using the 
other silently (Slack) makes less than zero sense to me.

And, for me, a tool is a tool, I'm not married to it (some people prefer vi 
editor and have religious attachments to it, I just use nano to get the job
done)

On Thu, Aug 22, 2019, 19:49 Nux!  wrote:

> I'm heavily against Slack or any other proprietary, closed solutions.
>
> I think it's a step back generally for the Internet at large and even 
> more so for an open source project; I can't reconcile the two in my 
> heart.
>
> Having said that, I believe the chat is dead not because it's IRC, but 
> because people prefer async comms (ie email). It'll be the same for 
> Slack.
>
>
> We should be promoting the mailing lists. They are active and the 
> archives are open to search engines etc and can further provide 
> helpful information to everyone.
>
> I won't -1 the decision, I don't want to be in the way of "progress", 
> but it's not a +1 either. I won't be using it.
>
> My 2p
>
>
> ---
> Sent from the Delta quadrant using Borg technology!
>
> On 2019-08-22 16:57, Andrija Panic wrote:
> > Hi guys,
> >
> > Since IRC is pretty dead, and we already have a Slack channel ( 
> > https://apachecloudstack.slack.com ) that we use atm, AND since 
> > there seems to be an official ASF slack channel at 
> > https://the-asf.slack.com/, I would like to open a discussion of the 
> > idea to "officially"  move (i.e.
> > marketing
> > this on all event pages and main web site) to that new CloudStack 
> > channel on the official ASF slack account/page - and abandon (close 
> > for good) all others chat channels.
> >
> > i.e. on this year conference page (http://us.cloudstackcollab.org/) 
> > we currently announce the IRC channel (???) to be the one (and AFAIK 
> > it's pretty dead) - so I would propose to move forward and update 
> > this, so the users can be aware of "alive" chat channel
> >
> > Suggestions, opinions ?
> >
> > Regards,
> >
> > Andrija Panić
>

FW: [VOTE] Apache CloudStack 4.13.0.0 RC1

[Paul Angus]

Hi All,

I've created a 4.13.0.0 release (RC1), with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535
Commit: 8e08b47cc952b9e2835da2fdee26ca0a94a4433e

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/

PGP release keys (signed using 51EE0BC8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 27th August 2019

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from 
8e08b47cc952b9e2835da2fdee26ca0a94a4433e and published RC1 repository here:
http://packages.shapeblue.com/testing/41300rc1/

The systemvm templates are unchanged from 4.11.3/4.12.0:
http://download.cloudstack.org/systemvm/4.11/



The PRs which have been added 4.13.0.0 since 4.12.0.0 are as follows:

+-+--+---+--++
| Version | Github   | Type  | Priority | Description   
 |
+=+==+===+==++
| 4.13.0.0| `#3564`_ |   |  | add vSphere 
6.7.3 and update 6.7.2 & 6.7.1 |
+-+--+---+--++
| 4.13.0.0| `#3560`_ |   |  | Display VM 
snapshot tags on usage records  |
+-+--+---+--++
| 4.13.0.0| `#3549`_ |   |  | add detailed 
hypervisor and guest OS data  |
+-+--+---+--++
| 4.13.0.0| `#3551`_ |   |  | Prevent 
NullPointer on a network with removed IP   |
| |  |   |  | 
ranges/"VLANs" |
+-+--+---+--++
| 4.13.0.0| `#3547`_ |   |  | 4.13/master 
stabilisation PR   |
+-+--+---+--++
| 4.13.0.0| `#3271`_ |   |  | VMware: Allow 
configuring appliances on the VM instance|
| |  |   |  | wizard when 
OVF properties are available   |
+-+--+---+--++
| 4.13.0.0| `#3545`_ |   |  | ui: fix for 
custom constrained offering params range check |
+-+--+---+--++
| 4.13.0.0| `#3533`_ |   |  | KVM local 
migration issue #3521|
+-+--+---+--++
| 4.13.0.0| `#3535`_ |   |  | Misc fixes to 
sharing templates functionality  |
+-+--+---+--++
| 4.13.0.0| `#3534`_ |   |  | Misc fixes 
around API permissions, global settings and |
| |  |   |  | template UX   
 |
+-+--+---+--++
| 4.13.0.0| `#3480`_ |   |  | engine, 
server, services: fix for respecting secondary |
| |  |   |  | storage 
threshold limit|
+-+--+---+--++
| 4.13.0.0| `#3529`_ |   |  | Add size to 
list usage records for VMSnapShotOnPrimary |
| |  | 

[VOTE] Apache CloudStack 4.13.0.0 RC1

[Paul Angus]

Hi All,

I've created a 4.13.0.0 release (RC1), with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.13.0.0-RC20190820T1535
Commit: 8e08b47cc952b9e2835da2fdee26ca0a94a4433e

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.13.0.0/

PGP release keys (signed using 51EE0BC8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 27th August 2019

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from 
8e08b47cc952b9e2835da2fdee26ca0a94a4433e and published RC1 repository here:
http://packages.shapeblue.com/testing/41300rc1/

The systemvm templates are unchanged from 4.11.3/4.12.0:
http://download.cloudstack.org/systemvm/4.11/



The PRs which have been added 4.13.0.0 since 4.12.0.0 are as follows:

+-+--+---+--++
| Version | Github   | Type  | Priority | Description   
 |
+=+==+===+==++
| 4.13.0.0| `#3564`_ |   |  | add vSphere 
6.7.3 and update 6.7.2 & 6.7.1 |
+-+--+---+--++
| 4.13.0.0| `#3560`_ |   |  | Display VM 
snapshot tags on usage records  |
+-+--+---+--++
| 4.13.0.0| `#3549`_ |   |  | add detailed 
hypervisor and guest OS data  |
+-+--+---+--++
| 4.13.0.0| `#3551`_ |   |  | Prevent 
NullPointer on a network with removed IP   |
| |  |   |  | 
ranges/"VLANs" |
+-+--+---+--++
| 4.13.0.0| `#3547`_ |   |  | 4.13/master 
stabilisation PR   |
+-+--+---+--++
| 4.13.0.0| `#3271`_ |   |  | VMware: Allow 
configuring appliances on the VM instance|
| |  |   |  | wizard when 
OVF properties are available   |
+-+--+---+--++
| 4.13.0.0| `#3545`_ |   |  | ui: fix for 
custom constrained offering params range check |
+-+--+---+--++
| 4.13.0.0| `#3533`_ |   |  | KVM local 
migration issue #3521|
+-+--+---+--++
| 4.13.0.0| `#3535`_ |   |  | Misc fixes to 
sharing templates functionality  |
+-+--+---+--++
| 4.13.0.0| `#3534`_ |   |  | Misc fixes 
around API permissions, global settings and |
| |  |   |  | template UX   
 |
+-+--+---+--++
| 4.13.0.0| `#3480`_ |   |  | engine, 
server, services: fix for respecting secondary |
| |  |   |  | storage 
threshold limit|
+-+--+---+--++
| 4.13.0.0| `#3529`_ |   |  | Add size to 
list usage records for VMSnapShotOnPrimary |
| |  |  

RE: Filtering DHCP traffic

[Paul Angus]

Fariborz,

It's a tricky problem you have.   You could reverse the problem by creating a 
VM yourself on that network and seeing what the IP/MAC address is of the DHCP 
server that gives it an address is (via the console proxy), then use that to 
trace the DHCP VM and owner. Then ask them to 'stop it (or else)'

Kind regards

Paul


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


-Original Message-
From: Ivan Kudryavtsev  
Sent: 09 August 2019 03:29
To: users 
Subject: Re: Filtering DHCP traffic

Even when no SGs used, the agent still creates iptables/ebtables rules and 
should block mac/ip spoofing, wrong dhcp announces. Im not sure how it works in 
the current CS version, but believe it:

- either local bug which must be investigated thru agent logs and 
iptables/ebtables dumps

- cs bug which was introduced recently.

We have ancient acs 4.3 with basic zone without sg and no dhcp faking works 
there. Unfortunately now all my zones with SGs, so cannot check...

пт, 9 авг. 2019 г., 4:17 Andrija Panic :

> Nope, that is the reason security groups should be used in 
> multi-tenant shared network... At least I'm not aware that is possible.
> Not sure if hacking the DB is possible though...
>
> On Thu, 8 Aug 2019, 20:58 Fariborz Navidan,  wrote:
>
> > Hello,
> > I have found a user VM who is running a sort of DHCP server i.e. a 
> > VPN server, etc. User VM is on default shared network without 
> > security groups enabled in a Basic zone which does not spport 
> > multiple networks. Is there any way to either enable security groups 
> > on existing network and add rule to stop VMs offer DHCP and prevent 
> > conflicting with VR's DHCP or manually add a firewall rule on VR to filter 
> > DHCP traffic from user VMs?
> >
> > TIA
> >
>

[ANNOUNCE] Apache CloudStack - Newsweek, Best Business Tools 2019 in 'Cloud Services'

[Paul Angus]

Hi Everyone,

I'm delighted to say that 'we' have been recognised by Newsweek in their 
inaugural list of Best Business Tools in the 'Cloud Services' category.
https://www.newsweek.com/best-business-tools-2019/cloud-services

A quick screen grab of the certificate can be found here:
https://imgur.com/a/7epEqeX

The recognition was for:
- Willingness to recommend the brand to colleagues
- Trustworthiness
- Reliability
- Fulfilment of service promise
- Continuous improvement
- Security

Well done everyone, this is a great community achievement and shows that not 
only is CloudStack great, but the world is starting to take notice of it too!


We'll upload the a good copy of the certificate to the ACS website and a bit of 
marketing stuff around it soon.


Paul Angus
CloudStack PMC
#CloudStackWorks


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

RE: management cluster error on cloudstack-management startup

[Paul Angus]

I think that this 'error' has been in the logs during startup 'forever'.  When 
the service starts up it tries to connect to all other mgmt. servers (including 
itself). As 'itself' isn't up yet, the error is output.  I guess that it's such 
a minor presentational thing that no one has ever got round to fixing it.

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


-Original Message-
From: Andrija Panic  
Sent: 26 July 2019 21:10
To: users 
Subject: Re: management cluster error on cloudstack-management startup

That error or "error" is present when starting mgmt server - but it does start 
correctly. Not sure if this is by design or a valid "error" - but doesn't 
affect anything (right ?)  Perhaps someone else can advise.

On Fri, 26 Jul 2019 at 19:43, Richard Persaud 
wrote:

> Hello,
>
>
>
> 4.11.3 on Ubuntu
>
>
>
> I get this error, even on a new build. I am not running mgmt in a cluster.
> Any ideas?
>
>
>
> Unable to ping management server at 10.0.0.9:9090 due to 
> ConnectException
>
> java.net.ConnectException: Connection refused
>
> at sun.nio.ch.Net.connect0(Native Method)
>
> at sun.nio.ch.Net.connect(Net.java:454)
>
> at sun.nio.ch.Net.connect(Net.java:446)
>
> at 
> sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
>
> at
> com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManager
> Impl.java:1137)
>
> at
> com.cloud.cluster.ClusterManagerImpl.pingManagementNode(ClusterManager
> Impl.java:1106)
>
> at
> com.cloud.cluster.ClusterManagerImpl.checkConflicts(ClusterManagerImpl
> .java:1184)
>
> at
> com.cloud.cluster.ClusterManagerImpl.configure(ClusterManagerImpl.java
> :1062)
>
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.w
> ith(CloudStackExtendedLifeCycle.java:115)
>
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.wit
> h(CloudStackExtendedLifeCycle.java:154)
>
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.con
> figure(CloudStackExtendedLifeCycle.java:111)
>
> at
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.sta
> rt(CloudStackExtendedLifeCycle.java:56)
>
> at
> org.springframework.context.support.DefaultLifecycleProcessor.doStart(
> DefaultLifecycleProcessor.java:183)
>
> at
> org.springframework.context.support.DefaultLifecycleProcessor.access$2
> 00(DefaultLifecycleProcessor.java:52)
>
> at
> org.springframework.context.support.DefaultLifecycleProcessor$Lifecycl
> eGroup.start(DefaultLifecycleProcessor.java:358)
>
> at
> org.springframework.context.support.DefaultLifecycleProcessor.startBea
> ns(DefaultLifecycleProcessor.java:159)
>
> at
> org.springframework.context.support.DefaultLifecycleProcessor.onRefres
> h(DefaultLifecycleProcessor.java:123)
>
> at
> org.springframework.context.support.AbstractApplicationContext.finishR
> efresh(AbstractApplicationContext.java:884)
>
> at
> org.springframework.context.support.AbstractApplicationContext.refresh
> (AbstractApplicationContext.java:552)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.loadContext(DefaultModuleDefinitionSet.java:145)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set$2.with(DefaultModuleDefinitionSet.java:122)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.withModule(DefaultModuleDefinitionSet.java:245)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.withModule(DefaultModuleDefinitionSet.java:250)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.withModule(DefaultModuleDefinitionSet.java:250)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.withModule(DefaultModuleDefinitionSet.java:233)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.loadContexts(DefaultModuleDefinitionSet.java:117)
>
> at
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinition
> Set.load(DefaultModuleDefinitionSet.java:79)
>
> at
> org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.
> loadModules(ModuleBasedContextFactory.java:37)
>
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.in
> it(CloudStackSpringContext.java:71)
>
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext. nit>(CloudStackSpringContext.java:58)
>
> at
> org.apache.cloudstack.spring.module.factory.CloudStackSpringContext. nit>(CloudStackSpringContext.java:62)
>
> at
> org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene
> 

[ANNOUNCE] Nathan Johnson has joined the PMC

[Paul Angus]

Fellow CloudStackers,



It gives me great pleasure to say that Nathan has been invited to join the
PMC and has gracefully accepted.


Please join me in congratulating Nathan!




Kind regards,



Paul Angus

CloudStack PMC

[ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

[Paul Angus]

Fellow CloudStackers,



It gives me great pleasure to say that Bobby has been invited to join the
PMC and has gracefully accepted.



Please join me in congratulating  Bobby!





Kind regards,





Paul Angus

CloudStack PMC

[ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

[Paul Angus]

Fellow CloudStackers,


Its non-stop today!



It gives me great pleasure to say that Gabriel has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC

[ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.3.0

[Paul Angus]

Announcing Apache CloudStack LTS Maintenance Release 4.11.30



The Apache CloudStack project is pleased to announce the release of
CloudStack 4.11.3.0 as part of its LTS 4.11.x releases. The CloudStack
4.11.3.0 release contains c. 50 fixes on top of the CloudStack 4.11.2.0
release. CloudStack LTS branches are supported for 20 months and will
receive updates for the first 14 months. For the final six months, only
security updates are provided.



Apache CloudStack is an integrated Infrastructure-as-a-Service (IaaS)
software platform allowing users to build feature-rich public and private
cloud environments. CloudStack includes an intuitive user interface and
rich API for managing the compute, networking, software, and storage
resources. The project became an Apache top level project in March, 2013.
More information about Apache CloudStack can be found at:

http://cloudstack.apache.org/



# Documentation



The 4.11.3.0 release notes include a full list of issues fixed:

http://docs.cloudstack.apache.org/en/4.11.3.0/releasenotes/fixed_issues.html




The CloudStack documentation includes upgrade instructions from previous
versions of Apache CloudStack, and can be found at:

http://docs.cloudstack.apache.org/en/4.11.3.0/upgrading/index.html


The official installation, administration and API documentation for each of
the releases are available on our documentation page:

http://docs.cloudstack.apache.org/



# Downloads



The official source code for the 4.11.3.0 release can be downloaded from
our downloads page:

http://cloudstack.apache.org/downloads.html



In addition to the official source code release, individual contributors
have also made convenience binaries available on the Apache CloudStack
download page, and can be found at:


http://download.cloudstack.org/ubuntu/dists/

http://download.cloudstack.org/centos/6/

http://download.cloudstack.org/centos/7/

http://www.shapeblue.com/packages/



Kind regards,



Paul Angus

[ANNOUNCE] Sven Vogel has joined the PMC

[Paul Angus]

Fellow CloudStackers,



It gives me great pleasure to say that Sven has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Sven!




Kind regards,



Paul Angus

CloudStack PMC

[ANNOUNCE] Andrija Panic has joined the PMC

[Paul Angus]

Fellow CloudStackers,



It gives me great pleasure to say that Adrija has been invited to join the
PMC and has gracefully accepted.


Please joining me in congratulating Andrija!




Kind regards,



Paul Angus

CloudStack PMC

RE: cloudstack container service (CCS)

[Paul Angus]

Hi Richard, 

CCS is not (yet) part of Apache CloudStack.
You need to contact ShapeBlue directly for any assistance with it.  As a quick 
tip, sourcecode can be built to work with 4.11 but I don't believe that the 
binaries which are compatible with 4.11 have been made available.

Kind regards


Paul


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


-Original Message-
From: Richard Persaud  
Sent: 08 July 2019 19:46
To: users@cloudstack.apache.org
Subject: cloudstack container service (CCS)

I am attempting to install the container service (ShapeBlue) on 4.11 running on 
Ubuntu 16.04 LTS.

I am following this guide 
http://downloads.shapeblue.com/ccs/1.0/Installation_and_Administration_Guide.pdf

Everything seemingly installs OK.

However, when launching a cluster, it is "stuck" in the starting state. The 
instances show up and in a running state. The CCS dashboard section only shows 
"Container cluster setup is under progress, please check again in few minutes."

I don't see anything out of the ordinary in the management logs, but not sure 
what I should be looking for.

Any ideas on where to start troubleshooting?

Regards,

Richard Persaud

RE: Unable to log in to the cloudstack management page (Web UI)

[Paul Angus]

Hi Sagawa,

That version of CloudStack is very old, the amount of help we're going to be 
able to give is going to be a bit limited.

The first thing I would check is that you have a commands.properties file.  I 
think back then it was in /etc/cloudstack/cloudstack-management (something like 
that)





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


-Original Message-
From: sagawa_e...@fujitsu.com  
Sent: 03 July 2019 10:17
To: 'users@cloudstack.apache.org' 
Cc: shigemoto.ya...@fujitsu.com; t-hoshik...@fujitsu.com
Subject: Unable to log in to the cloudstack management page (Web UI)

Hello,

I am unable to log in to the cloudstack management page (Web UI).
The details of the error are as follows.

I appreciate very much if you could tell me some advice, comments or how to 
solve the problem.

==

[0]system
  OS：CentOS 6.3 64bit
  Cloudstack version : Apache CloudStack 4.2.1

[1]trouble
Unable to log in to the cloudstack management page (Web UI)
Even if the login button is clicked, no alert is displayed on the screen, 
and it seems that there is no particular response.
However, in the HTTP access log, error messages in the 300th (304) and 
400th (401, 404) HTTP status codes are included.
An error may have occurred in cloudstack internal processing when a 401 
error is generated.

[2]Log messages after clicking on a login button

  2-1. access_log.2019-07-01.txt
-
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/infrastructure/infrastructure.js HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/vpc/vpc.js HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/vpc/vpc.css HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/infrastructure/infrastructure.css HTTP/1.1" 404 1082
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/vnmcNetworkProvider/vnmcNetworkProvider.css HTTP/1.1" 404 1112
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/api?command=listCapabilities=json=null&_=1561961364158
 HTTP/1.1" 401 101
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/images/logo-login-oss.png HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/images/sprites.png HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/images/bg-login.png HTTP/1.1" 304 -
192.168.122.1 - - [01/Jul/2019:06:09:22 +0900] "GET 
/client/modules/vnmcAsa1000v/vnmcAsa1000v.css HTTP/1.1" 404 1070
-

Status code of /client/api is a 401 error (Unauthorized).

  2-2. apilog.log
-
2019-07-01 06:09:23,174 INFO  [cloud.api.ApiServer] (catalina-exec-3:null)  
192.168.122.1 -- GET 
command=listCapabilities=json=null&_=1561961364158 401 
unable to verify user credentials
-

apilog.log contains the above message at the same time when 401 error 
occurred.

  2-3. other log output
-
==> /var/log/cloudstack/management/management-server.log <==
2019-07-01 06:13:10,731 DEBUG [cloud.api.ApiServlet] 
(catalina-exec-17:null) ===START===  192.168.122.1 -- POST  
2019-07-01 06:13:10,745 DEBUG [cloud.user.AccountManagerImpl] 
(catalina-exec-17:null) Attempting to log in user: admin in domain 1
2019-07-01 06:13:10,745 DEBUG [server.auth.SHA256SaltedUserAuthenticator] 
(catalina-exec-17:null) Retrieving user: admin
2019-07-01 06:13:10,911 DEBUG [cloud.user.AccountManagerImpl] 
(catalina-exec-17:null) User: admin in domain 1 has successfully logged in

==> /var/log/cloudstack/management/apilog.log <==
2019-07-01 06:13:10,945 INFO  [cloud.api.ApiServer] (catalina-exec-17:null) 
(userId=2 accountId=2 sessionId=11305223FB11770BC8715A8C6220C036) 192.168.122.1 
-- POST command=login domain=/

==> /var/log/cloudstack/management/management-server.log <==
2019-07-01 06:13:10,946 DEBUG [cloud.api.ApiServlet] 
(catalina-exec-17:null) ===END===  192.168.122.1 -- POST  
2019-07-01 06:13:10,963 DEBUG [cloud.api.ApiServlet] 
(catalina-exec-22:null) ===START===  192.168.122.1 -- GET  
command=listCapabilities=json=h1Lwsk9dqVwZxGAwk0owzFDtmi4%3D&_=1561961591972
2019-07-01 06:13:10,976 DEBUG [cloud.api.ApiServer] (catalina-exec-22:null) 
The given command:listCapabilities does not exist or it is not available for 
user with id:2

==> /var/log/cloudstack/management/apilog.log <==
2019-07-01 06:13:10,979 INFO  [cloud.api.ApiServer] (catalina-exec-22:null) 
 192.168.122.1 -- GET 
command=listCapabilities=json=h1Lwsk9dqVwZxGAwk0owzFDtmi4%3D&_=1561961591972
 432 The given command does not exist or it is not available for user

==> 

[VOTE][RESULT] Apache CloudStack 4.11.3.0

[Paul Angus]

Hi everyone,

After more than 72hrs the vote for CloudStack 4.11.3.0 rc2 *passes* with
3 PMC + 3 non-PMC votes.

+1 (PMC / binding)
Rohit Yadav
Wei Zhou
Milamber


+1 (non binding)
Boris Stoyanov
Nicolas Vazquez
Anurag Awasthi


0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to give 
the mirrors time to catch up.

 

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

[VOTE] CloudStack 4.11.3.0 RC2

[Paul Angus]

Hi All,

I've created a 4.11.3.0 release (RC2), with the following artefacts up for 
testing and a vote:


Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.3.0-RC20190625T2045
Commit: d895983d111086dd392a4bce257726b978465b43

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/

PGP release keys (signed using 51EE0BC8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 29th June.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from 
d895983d111086dd392a4bce257726b978465b43 and published RC2 repository here:
http://packages.shapeblue.com/testing/41130rc2/

The release notes are still work-in-progress, but the systemvm template upgrade 
section has been updated. You may refer the following for systemvm template 
upgrade testing:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html

4.11.3.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41130rc1/


One commit added since RC1
64d1316e60b2793768be91f1b4c2466695e5a927 | schema: add 4.11.2 to 4.11.3 
systemvmtemplate upgrade path



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

[VOTE][RESULT] Apache CloudStack 4.11.3.0

[Paul Angus]

Hi everyone,

After more than 72hrs the vote for CloudStack 4.11.3.0 *passes* with
3 PMC + 1 non-PMC votes.

+1 (PMC / binding)
Rohit Yadav
Milamber (Bruno Demion)
Nux (Lucian)

+1 (non binding)
Gregor Riepl

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to give 
the mirrors time to catch up.







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


-Original Message-
From: Nux!  
Sent: 20 June 2019 09:35
To: dev 
Subject: Re: [VOTE] 4.11.3.0 RC1

+1 (binding)

KVM, CentOS7, local storage.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Milamber" 
> To: "dev" 
> Sent: Wednesday, 19 June, 2019 22:35:50
> Subject: Re: [VOTE] 4.11.3.0 RC1

> Hello,
> 
> +1 (binding)
> 
> 
> Tested on KVM + NFS installation
> 
> 
> Milamber
> 
> On 11/06/2019 10:57, Paul Angus wrote:
>> Hi All,
>>
>> I've created a 4.11.3.0 release (RC1), with the following artefacts 
>> up for testing and a vote:
>>
>>
>> Git Branch and Commit SH:
>> https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>> s/heads/4.11.3.0-RC20190610T1615
>> Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302
>>
>> Source release (checksums and signatures are available at the same
>> location):
>> https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/
>>
>> PGP release keys (signed using 51EE0BC8):
>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>
>> The vote will be open until end of 16 June 2019.
>>
>> For sanity in tallying the vote, can PMC members please be sure to 
>> indicate "(binding)" with their vote?
>>
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>> Additional information:
>>
>> For users' convenience, I've built packages from
>> 51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here:
>> http://packages.shapeblue.com/testing/41130rc1/
>>
>> The release notes are still work-in-progress, but the systemvm 
>> template upgrade section has been updated. You may refer the 
>> following for systemvm template upgrade testing:
>> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/e
>> n/latest/index.html
>>
>> 4.11.3.0 systemvm templates are available from here:
>> http://packages.shapeblue.com/testing/systemvm/41130rc1/
>>
>>
>>
>> PRs in 4.11.3.0:
>> +==+
>>
>> +-+--++
>> | Version | Github   | Description
>> | |
>> +=+==+===
>> +=+
>> | 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3
>> | systemvmtemplate upgrade path |
>> +-+--++
>> | 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on
>> | provisionCertificate |
>> | |  | API   
>>  |
>> +-+--++
>> | 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC
>> | |
>> +-+--++
>> | 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT 
>> rules
>> | |
>> +-+--++
>> | 4.11.3.0| `#3194`_ | Suspending a VM before snapshot 
>> deletion
>> | (see PR #3193)|
>> +-+--++
>> | 4.11.3.0| `#3370`_ | ssvm: apply MTU value on 
>> storage/management
>> | nic if |
>> | |  | available 
>>  |
>> +-+--++
>> | 4.11.3.0| `#2995`_ | KVM: Improvements on upload direct 
>> download
>> | certificates   |
>> +-+--++
>> | 4.11.3.0  

[VOTE] 4.11.3.0 RC1

[Paul Angus]

Hi All,

I've created a 4.11.3.0 release (RC1), with the following artefacts up for 
testing and a vote:


Git Branch and Commit SH:
https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.3.0-RC20190610T1615
Commit: 51124b7b35f47089b2e51a93b2094ea93dd15302

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.11.3.0/

PGP release keys (signed using 51EE0BC8):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until end of 16 June 2019.

For sanity in tallying the vote, can PMC members please be sure to indicate 
"(binding)" with their vote?

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Additional information:

For users' convenience, I've built packages from 
51124b7b35f47089b2e51a93b2094ea93dd15302 and published RC1 repository here:
http://packages.shapeblue.com/testing/41130rc1/

The release notes are still work-in-progress, but the systemvm template upgrade 
section has been updated. You may refer the following for systemvm template 
upgrade testing:
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html

4.11.3.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41130rc1/



PRs in 4.11.3.0:
+==+

+-+--++
| Version | Github   | Description  
  |
+=+==++
| 4.11.3.0| `#3381`_ | schema: add 4.11.2 to 4.11.3 
systemvmtemplate upgrade path |
+-+--++
| 4.11.3.0| `#3075`_ | KVM: Prevent regenerating keystore on 
provisionCertificate |
| |  | API  
  |
+-+--++
| 4.11.3.0| `#3373`_ | router: support multi-homed VMs in VPC   
  |
+-+--++
| 4.11.3.0| `#3366`_ | Fix rule duplication with static NAT 
rules |
+-+--++
| 4.11.3.0| `#3194`_ | Suspending a VM before snapshot deletion 
(see PR #3193)|
+-+--++
| 4.11.3.0| `#3370`_ | ssvm: apply MTU value on 
storage/management nic if |
| |  | available
  |
+-+--++
| 4.11.3.0| `#2995`_ | KVM: Improvements on upload direct 
download certificates   |
+-+--++
| 4.11.3.0| `#3351`_ | Have persistent DHCP leases file on VRs 
and cleanup|
| |  | /etc/hosts on VM deletion
  |
+-+--++
| 4.11.3.0| `#3310`_ | Fix removing static NAT rules with 
Juniper SRX |
+-+--++
| 4.11.3.0| `#3361`_ | Fix 4.11 VR Issues with Multiple Public 
Subnets|
+-+--++
| 4.11.3.0| `#3206`_ | server: allow dedicate ip range to a 
domain if ips are |
| |  | used by an account in the domain 
  |
+-+--++
| 4.11.3.0| `#3205`_ | server: update dhcp configurations in 
vrs while update |
| |  | default nic of running vms   
  |
+-+--++
| 4.11.3.0| `#3362`_ | vmware: fix potential NPE when memory 
hotplug capability   |
| |  | is checked   
  |
+-+--++
| 4.11.3.0| `#3338`_ | ui: fix enable static nat only towards 
first nic and not   |
|   

4.13 Heads up

[Paul Angus]

In order to keep up the momentum on the release cadence, some of us are now 
planning to get 4.13 moving



We've come up with a plan which I hope everyone will find acceptable (see 
below).





==  4.13.0.0: (next LTS release) ==



  *   1-5 July 2019: Freeze master and stabilize
  *   8-12 July 2019: After ~100% smoketest pass and only accept blocker fixes, 
cut RC1
  *   14 July - 5 Aug 2019: Release 4.13.0.0 (next LTS)
  *   Milestone: https://github.com/apache/cloudstack/milestone/8



Cheers



Paul Angus












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

RE: Can't start systemVM in a new advanced zone deployment

[Paul Angus]

Hi Yiping,

do you have snapshots enabled on the NetApp filer?  (it used to be seen as a  
".snapshot"  subdirectory in each directory)

If so try disabling snapshots - there used to be a bug where the .snapshot 
directory would confuse CloudStack.

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


-Original Message-
From: Yiping Zhang  
Sent: 05 June 2019 23:38
To: users@cloudstack.apache.org
Subject: Re: Can't start systemVM in a new advanced zone deployment

Hi, Sergey:

I found more logs in vpxa.log ( the esxi hosts are using UTC time zone,  so I 
was looking at wrong time periods earlier).  I have uploaded more logs into 
pastebin.

From these log entries,  it appears that when copying template to VM,  it tried 
to open destination VMDK file and got error file not found.  

In case that the CloudStack attempted to create a systemVM,  the destination 
VMDK file path it is looking for is "//.vmdk", 
 see uploaded log at https://pastebin.com/aFysZkTy

In case when I manually created new VM from a (different) template in vCenter 
UI,   the destination VMDK file path it is looking for is 
"//.vmdk", see uploaded log at 
https://pastebin.com/yHcsD8xB

So, I am confused as to how the path for destination VMDK was determined and by 
CloudStack or VMware, how did I end up with this?

Yiping


On 6/5/19, 12:32 PM, "Sergey Levitskiy"  wrote:

Some operations log get transferred to vCenter log vpxd.log. It is not 
straightforward to trace I but Vmware will be able to help should you open case 
with them. 


On 6/5/19, 11:39 AM, "Yiping Zhang"  wrote:

Hi, Sergey:

During the time period when I had problem cloning template,  there are 
only a few unique entries in vmkernel.log, and they were repeated 
hundreds/thousands of times by all the cpu cores:

2019-06-02T16:47:00.633Z cpu9:8491061)FSS: 6751: Failed to open file 
'hpilo-d0ccb15'; Requested flags 0x5, world: 8491061 [ams-ahs], (Existing flags 
0x5, world: 8491029 [ams-main]): Busy
2019-06-02T16:47:49.320Z cpu1:66415)nhpsa: hpsa_vmkScsiCmdDone:6384: 
Sense data: error code: 0x70, key: 0x5, info:00 00 00 00 , cmdInfo:00 00 00 00 
, CmdSN: 0xd5c, worldId: 0x818e8e, Cmd: 0x85, ASC: 0x20, ASCQ: 0x0
2019-06-02T16:47:49.320Z cpu1:66415)ScsiDeviceIO: 2948: 
Cmd(0x43954115be40) 0x85, CmdSN 0xd5c from world 8490638 to dev 
"naa.600508b1001c6d77d7dd6a0cc0953df1" failed H:0x0 D:0x2 P:0x0 Valid sense 
data: 0x5 0x20 0x0.

The device " naa.600508b1001c6d77d7dd6a0cc0953df1" is the local disk on 
this host.

Yiping


On 6/5/19, 11:15 AM, "Sergey Levitskiy"  wrote:

This must be specific to that environment.  For a full clone mode 
ACS simply calls cloneVMTask of vSphere API so basically until cloning of that 
template succeeds when attmepted in vSphere client  it would keep failing in 
ACS. Can you post vmkernel.log from your ESX host esx-0001-a-001?


On 6/5/19, 8:47 AM, "Yiping Zhang"  
wrote:

Well,  I can always reproduce it in this particular vSphere set 
up,  but in a different ACS+vSphere environment,  I don't see this problem.

Yiping

On 6/5/19, 1:00 AM, "Andrija Panic"  
wrote:

Yiping,

if you are sure you can reproduce the issue, it would be 
good to raise a
GitHub issue and provide as much detail as possible.

Andrija

On Wed, 5 Jun 2019 at 05:29, Yiping Zhang 

wrote:

> Hi, Sergey:
>
> Thanks for the tip. After setting 
vmware.create.full.clone=false,  I was
> able to create and start system VM instances.However, 
 I feel that the
> underlying problem still exists, and I am just working 
around it instead of
> fixing it,  because in my lab CloudStack instance with 
the same version of
> ACS and vSphere,  I still have 
vmware.create.full.clone=true and all is
> working as expected.
>
> I did some reading on VMware docs regarding full clone 
vs. linked clone.
> It seems that the best practice is to use full clone for 
production,
> especially if there are high rates of changes to the 
disks.  So
> eventually,  I need to understand and fix the root cause 
for this issue.
> At least for now,  I am over this hurdle and I can move 
on.
>
> Thanks again,
>
 

RE: Getting Cracking on a 4.11.3

[Paul Angus]

Correction:   1 June 2019: Cut RC1**SHOULD READ  -->  10 July

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


-Original Message-
From: Paul Angus  
Sent: 23 May 2019 17:05
To: dev ; users@cloudstack.apache.org
Subject: Getting Cracking on a

Hi everyone,

This a little 'heads up'.  In order to try to get our release cadence back on 
track, some of us are planning to get cracking on a 4.11.3

We've come up with a plan which I hope everyone will find acceptable (see 
below).

Let the fun commence!!

4.11.3.0: (next current LTS minor release)
==

Until 3 June 2019: Accept any minor/major/critical/blocker fixes
3 June - 10 June 2019: Stabilise 4.11 branch
1 June 2019: Cut RC1**
11-24 June 2019: Release 4.11.3.0
Milestone: https://github.com/apache/cloudstack/milestone/7


** With 4.11 branch already stable, we hope the effort towards stabilizing be 
minimal



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

Getting Cracking on a

[Paul Angus]

Hi everyone,



This a little 'heads up'.  In order to try to get our release cadence back on 
track, some of us are planning to get cracking on a 4.11.3

We've come up with a plan which I hope everyone will find acceptable (see 
below).



Let the fun commence!!





4.11.3.0: (next current LTS minor release)

==



Until 3 June 2019: Accept any minor/major/critical/blocker fixes

3 June - 10 June 2019: Stabilise 4.11 branch

1 June 2019: Cut RC1**

11-24 June 2019: Release 4.11.3.0

Milestone: https://github.com/apache/cloudstack/milestone/7



** With 4.11 branch already stable, we hope the effort towards stabilizing be 
minimal






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

RE: [VOTE] Remove el6 support in future CloudStack versions (was Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14)

[Paul Angus]

+1 (Binding)

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


-Original Message-
From: Anurag Awasthi  
Sent: 21 May 2019 10:55
To: users@cloudstack.apache.org; dev 
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: 
[DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1


From: Dag Sonstebo 
Sent: Tuesday, May 21, 2019 3:22 PM
To: users@cloudstack.apache.org; dev
Subject: Re: [VOTE] Remove el6 support in future CloudStack versions (was Re: 
[DISCUSS] Remove support for el6 packaging in 4.13/4.14)

+1

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue


On 21/05/2019, 10:40, "Rohit Yadav"  wrote:

All,


Thank you for your feedback and discussions. From what we've discussed so 
far, we've lazy consensus that nobody wants to use el6 or are limited to 
upgrade to el7/el8 due to potential risks.


Moving forward I put forth the following for voting:


- Next minor/major releases (such as 4.11.3.0, 4.13.0.0) will be last ones 
to support el6 packaging both for the management server and KVM host, but users 
are discouraged from using them

- Next major release (4.13.0.0) will document in its release notes that 
we'll stop supporting centos6/rhel6 packaging in future versions, i.e. 4.14 and 
onwards

- After 4.13.0.0 is released, we will remove el6 related specs, packaging 
scripts etc. from the codebase in the master branch


[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


** PMCs kindly add binding to your votes, thanks.


Thanks.



Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com



From: Erik Weber 
Sent: Wednesday, April 24, 2019 19:32
To: dev
Subject: Re: [DISCUSS] Remove support for el6 packaging in 4.13/4.14

CentOS7 was released 5 years ago, upgrading is long overdue anyway.
Realistically the next CloudStack release won't be out the door for
another ~4-6 months either.

--
Erik

On Wed, Apr 24, 2019 at 3:27 PM Ron Wheeler
 wrote:
>
> According to https://en.wikipedia.org/wiki/CentOS
>
> CentOS 6 EOL is 2020
> CentOS 7 EOL is 2024
>
>
> +1 for removing support for CentOS 6.
>
> As Erik pointed out the sites running CentOS6 will have to move soon in
> any event and it is probably better to do it now when there is still a
> lot of current expertise and information available about how to do it
> and how to make any changes to applications.
>
> Upgrading in a project that is under your control is usually easier than
> one forced on you by a security issue or an operational failure.
>
> Ron
>
> On 4/24/19 3:24 AM, Erik Weber wrote:
> > As an operations guy I can understand the want for future updates and
> > not upgrading, but with the release plan of RHEL/CentOS I don't find
> > it feasible.
> >
> > RHEL6 is 8 years old (and is still running kernel 2.6!) and isn't
> > scheduled to be fully EOL until 2024.
> >
> > It is true that upgrading requires some effort (and risk) from
> > operators, but this is work they eventually have to do anyway, so it's
> > not a matter of /if/ they have to do it, but rather when.
> >
> > It is also true that current CloudStack releases should continue to
> > work, it's also possible that someone might back port future fixes to
> > a RHEL6 compatible fork (you're more than welcome to).
> >
> > I'd vote +1 to remove support for el6 packaging.
> >

rohit.ya...@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




anurag.awas...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
  
 

RE: issue with system vm template not downloading

[Paul Angus]

Richard,

From the logs, there seems to be an issue with your storage configuration.
It _looks_ like you have enabled 'local storage' and that the system vms are 
using that.
Did you explicitly add your NFS from each of the servers in the CloudStack GUI 
or API?  The built-in service offerings for VMs don't include ones for local 
storage, only shared storage.
As CloudStack can't find any shared storage, and the system vms appear to be 
running on local storage, it suggests to me that you only have local storage 
attached.

Regards


Paul.

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


-Original Message-
From: Richard Persaud  
Sent: 10 May 2019 22:45
To: users@cloudstack.apache.org
Cc: /usr/local/cloud/systemvm/ssvm-check...@gmail.com
Subject: RE: issue with system vm template not downloading

Hi Andrija,

Advanced zone.

I ran the ssvm-check.sh and I did correct some NFS errors. Now, ssvm-check.sh 
runs without any issues.

The situation seems to have worsened – now I am unable to deploy any VM:

http://www.filedropper.com/cs-mgmt-log2

I am getting an insufficient capacity error, but this is a new environment, so 
no guest VMs or guest Networks are created.

Regards,

Richard Persaud

From: Andrija Panic 
Sent: Friday, May 10, 2019 2:00 PM
To: users 
Cc: /usr/local/cloud/systemvm/ssvm-check...@gmail.com
Subject: Re: issue with system vm template not downloading

⚠ EXT MSG:

Hi Richard,

Can you also, beside logs, try/confirm the following:

- are you running a Basic zone ?
- since systemVM tempate should be pre-seeded with a script, perhaps you are 
having issues with the SSVM itself and/or downloading default CentOS template? 
If so please execute from inside SSVM the following script and provide results  
: 
/usr/local/cloud/systemvm/ssvm-check.sh<https://isolate.menlosecurity.com/0/eJyrViotylGyUsooKSmw0tcvLi7L1U3OSE3O1ivOUNJRKspXsjLUUSrJTAGqMTQwVqoFAI6zDuI>
 and send us the output.


Regards,
Andrija

On Fri, May 10, 2019, 17:52 Paul Angus 
mailto:paul.an...@shapeblue.com>> wrote:

> Richard,
>
> Could you post (using 
> pastebin.com<https://isolate.menlosecurity.com/0/eJyrViotylGyUsooKSmw0tcvSCwuSU3KzNNLzs9V0lEqyleyMtRRKslMASoxNDBWqgUAgOAOqA>
>  or similar) a large chunk of your management server logs around the time of 
> this error please.
> I would think that we need some context to the message.  'Storage host'
> usually refers to the SSVM itself, a timeout waiting for a response 
> _suggests_ that the SSVM has been deployed, but isn't 'checking-in'.  
> Much more of the log information would probably help, whatever the problem.
>
> Also...
> I can kinda see what you're trying to achieve with NFS on all of the 
> hosts
> - but I agree with Ivan, I think that you'll soon regret it.
>
>
> Regards
>
> Paul Angus
>
> paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
> www.shapeblue.com<https://isolate.menlosecurity.com/0/eJyrViotylGyUsoo
> KSmw0tcvLy_XK85ILEhNyilN1UvOz1XSUSrKV7Iy1FEqyUwBqjM0MFaqBQDf4BCe>
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Ivan Kudryavtsev 
> mailto:kudryavtsev...@bw-sw.com>>
> Sent: 10 May 2019 16:28
> To: users 
> mailto:users@cloudstack.apache.org>>
> Subject: Re: issue with system vm template not downloading
>
> Richard,
>
> 1. About bridges, just check traffic goes correctly between HV hosts 
> and SS. All your hosts should be able to mount SS.
> 2. About your HV/Storage topology.
>
> 1st. Cloudstack doesn't balance the storages. While the first chosen 
> storage is capable to deploy the image, it will be used. You will not 
> able to balance volumes between them.
> 2nd. Every HV will mount every storage. If HV fails (which is probably 
> happen more frequently than storage) it will cause __all the__ hosts 
> will meet the problem with the NFS share and kick reboot, so, all your 
> cloud will reboot.
> Frankly, it's the worst topology possible. What I recommend is to 
> switch either to Ceph or Gluster if you want shared storage, split all 
> the hosts to separate clusters or use LOCAL STORAGE instead of NFS 
> storage, so your VMS will use local storage. Later if you wish to move 
> VMs between hosts, you can do it manually.
>
> Best wishes
>
>
>
>
>
> пт, 10 мая 2019 г. в 20:14, Richard Persaud 
> mailto:richard.pers...@macys.com>>:
>
> > Hi Ivan,
> >
> > Thanks for the info.
> >
> > Will you clarify what I should be looking for in my bridge set up?
> > It's fairly standard other then setting the MTU to 9000.
> >
> > The host/storage devices are using hardware RAID5. And all 
> > hypervisors are capable of mounting any of the NFS 

RE: issue with system vm template not downloading

[Paul Angus]

Richard,

Could you post (using pastebin.com or similar) a large chunk of your management 
server logs around the time of this error please.  
I would think that we need some context to the message.  'Storage host' usually 
refers to the SSVM itself, a timeout waiting for a response _suggests_ that the 
SSVM has been deployed, but isn't 'checking-in'.  Much more of the log 
information would probably help, whatever the problem.

Also...
I can kinda see what you're trying to achieve with NFS on all of the hosts - 
but I agree with Ivan, I think that you'll soon regret it.


Regards

Paul Angus

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


-Original Message-
From: Ivan Kudryavtsev  
Sent: 10 May 2019 16:28
To: users 
Subject: Re: issue with system vm template not downloading

Richard,

1. About bridges, just check traffic goes correctly between HV hosts and SS. 
All your hosts should be able to mount SS.
2. About your HV/Storage topology.

1st. Cloudstack doesn't balance the storages. While the first chosen storage is 
capable to deploy the image, it will be used. You will not able to balance 
volumes between them.
2nd. Every HV will mount every storage. If HV fails (which is probably happen 
more frequently than storage) it will cause __all the__ hosts will meet the 
problem with the NFS share and kick reboot, so, all your cloud will reboot.
Frankly, it's the worst topology possible. What I recommend is to switch either 
to Ceph or Gluster if you want shared storage, split all the hosts to separate 
clusters or use LOCAL STORAGE instead of NFS storage, so your VMS will use 
local storage. Later if you wish to move VMs between hosts, you can do it 
manually.

Best wishes





пт, 10 мая 2019 г. в 20:14, Richard Persaud :

> Hi Ivan,
>
> Thanks for the info.
>
> Will you clarify what I should be looking for in my bridge set up? 
> It's fairly standard other then setting the MTU to 9000.
>
> The host/storage devices are using hardware RAID5. And all hypervisors 
> are capable of mounting any of the NFS shares.
>
> Will you give me some detail on what you mean when you say using 
> native RAID is a bad idea? Why is that and what is the recommended way to set 
> up?
>
> Thanks in advance
>
>
> Regards,
> Richard Persaud
> Sys Spec, Info Security Del | Macy's, Inc.
> 5985 State Bridge Rd. | Johns Creek, GA 30097
> Office: 678-474-2357
> https://macyspartners.com/PublishingImages/MakeLifeShineBrighter.png
>
> 
> From: Ivan Kudryavtsev 
> Sent: Thursday, May 9, 2019 21:57
> To: users
> Subject: Re: issue with system vm template not downloading
>
> ⚠ EXT MSG:
>
> Richard, the most probable problem is with bridge devices. Management 
> server doesn't care about systemvm. The only unit which cares - ssvm 
> and hypervisor. Also, if you are using naive RAID/NFS within one 
> cluster when any HV can mount any storage (mesh) it's extremely bad 
> idea. You will get s lot of reboots if any of node meets outage. If 
> you have DRBD or Gluster, then, it's fine.
>
> пт, 10 мая 2019 г., 6:32 Richard Persaud  <mailto:richard.pers...@macys.com>>:
>
> > Hello,
> >
> > Our setup:
> > 4.11 on Ubuntu 16.04 LTS. One management server, eight 
> > compute/storage hosts (dual function).
> > NFS for storage.
> > No firewall in between the mgmt server and the hosts.
> > Management and storage traffic run over the same VLAN (same network).
> >
> > We are having an issue with the system vm template not downloading.
> > We have seen this issue on multiple occasions
> >
> > "Timeout waiting for response from storage host"
> >
> > It does not give any further information.
> >
> > The management server can successfully contact and mount the NFS 
> > shares from all the compute/storage hosts.
> >
> > How can I determine which storage host is timing out? Why is it 
> > timing
> out?
> >
> > Regards,
> >
> > Richard Persaud
> >
>
> * This is an EXTERNAL EMAIL. Stop and think before clicking a link or 
> opening attachments.
>


--
With best regards, Ivan Kudryavtsev
Bitworks LLC
Cell RU: +7-923-414-1515
Cell USA: +1-201-257-1512
WWW: http://bitworks.software/ <http://bw-sw.com/>

RE: Restricting IP usage & Upgrading CloudStack & Live storage migration

[Paul Angus]

- The models are 'native' if you like, definitely not workarounds.

- CloudStack is an orchestrator, it largely relies on the abilities of the 
hypervisors that it orchestrates.  We add a little secret sauce here and there, 
but when it comes to basic hypervisor functions, we leave it up to the 
hypervisor.


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


-Original Message-
From: Razvan Rosca  
Sent: 01 May 2019 19:57
To: users@cloudstack.apache.org
Subject: Re: Restricting IP usage & Upgrading CloudStack & Live storage 
migration

Hey Paul,

Thank you for your fast reply!

> There are a few different models that you can use.
Do any of these models work "by default", or they are "workarounds"
(similar to Proxmox / LXC)? Aka is this a native/direct solution that can be 
applied in the VM creation flow?

> Yes CloudStack does support Xen Live Storage migration
I was referring to something *similar* with Xen Live Storage migration, not Xen 
Live Storage "per se". Aka migrate a VM from a CloudStack node to another 
CloudStack node, natively, live, without using a central storage.

Thank you,
Razvan Rosca

Skype: razvan.rosca
Tel: +40 731 059 660
Linkedin: https://www.linkedin.com/in/razvanrosca/
Facebook: https://fb.com/razvanrosca.com


On Wed, May 1, 2019 at 9:50 PM Paul Angus  wrote:

> Hi Razvan,
>
> - There are a few different models that you can use.  But in short - 'yes'
> you can have a model where an IP is allocated to a VM and the VM keeps it.
> - No, we spend a lot of time making sure that upgrades between all 
> versions work. Our versioning system requires that the API is backward 
> compatible and we can only break that with a major version upgrade 
> (say 4.x to 5.x )and that hasn't happened under Apache yet
> - Yes CloudStack does support Xen Live Storage migration - 
> http://docs.cloudstack.apache.org/en/latest/adminguide/storage.html?hi
> ghlight=live%20storage#storage-overview
>
> Cheers
>
> Paul.
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Razvan Rosca 
> Sent: 01 May 2019 17:28
> To: users@cloudstack.apache.org
> Subject: Restricting IP usage & Upgrading CloudStack & Live storage
> migration
>
> Hello,
>
> We're thinking about switching from our current Xen+Proxmox setup into
> something more "advanced", and we're really considering CloudStack as one
> of our best/main candidates.
>
> Right off the bat here are the first questions:
>
>- in our current setup users can freely use each other's IP address,
>because the software stack doesn't enforce any limits (or requires us to
>manually edit stuff each time a VM is created). Does CloudStack have the
>same behavior? What we need is kinda simple: allow a specific VM to use
> a
>specific IP, and only that IP.
>- does CloudStack have the same "no-upgrade" policy as OpenStack?
>Ugrading OpenStack was/is nearly impossible, so I'm wondering if this is
>the case with CloudStack as well.
>- does CloudStack support "live-migration" between local storages? Xen
>does it, and does it really well. Again, I'm referring to local storage
>(local HDD/SSD/NVMe), not a central Ceph/Gluster/NFS store.
>
> Thank you,
> Razvan Rosca
>
> Skype: razvan.rosca
> Tel: +40 731 059 660
> Linkedin: https://www.linkedin.com/in/razvanrosca/
> Facebook: https://fb.com/razvanrosca.com
>

RE: Restricting IP usage & Upgrading CloudStack & Live storage migration

[Paul Angus]

Hi Razvan,

- There are a few different models that you can use.  But in short - 'yes' you 
can have a model where an IP is allocated to a VM and the VM keeps it.
- No, we spend a lot of time making sure that upgrades between all versions 
work. Our versioning system requires that the API is backward compatible and we 
can only break that with a major version upgrade (say 4.x to 5.x )and that 
hasn't happened under Apache yet 
- Yes CloudStack does support Xen Live Storage migration - 
http://docs.cloudstack.apache.org/en/latest/adminguide/storage.html?highlight=live%20storage#storage-overview

Cheers

Paul.



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


-Original Message-
From: Razvan Rosca  
Sent: 01 May 2019 17:28
To: users@cloudstack.apache.org
Subject: Restricting IP usage & Upgrading CloudStack & Live storage migration

Hello,

We're thinking about switching from our current Xen+Proxmox setup into 
something more "advanced", and we're really considering CloudStack as one of 
our best/main candidates.

Right off the bat here are the first questions:

   - in our current setup users can freely use each other's IP address,
   because the software stack doesn't enforce any limits (or requires us to
   manually edit stuff each time a VM is created). Does CloudStack have the
   same behavior? What we need is kinda simple: allow a specific VM to use a
   specific IP, and only that IP.
   - does CloudStack have the same "no-upgrade" policy as OpenStack?
   Ugrading OpenStack was/is nearly impossible, so I'm wondering if this is
   the case with CloudStack as well.
   - does CloudStack support "live-migration" between local storages? Xen
   does it, and does it really well. Again, I'm referring to local storage
   (local HDD/SSD/NVMe), not a central Ceph/Gluster/NFS store.

Thank you,
Razvan Rosca

Skype: razvan.rosca
Tel: +40 731 059 660
Linkedin: https://www.linkedin.com/in/razvanrosca/
Facebook: https://fb.com/razvanrosca.com

RE: Troubleshooting the Exception "Unable to start VM instance"

[Paul Angus]

Hi Peter,

We'd be able to help best if you post a whole unedited chunk of the management 
log from the time you attempt to start this VM.  You need to use something like 
pastebin.com as you can't add attachments on the mailing lists.

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


-Original Message-
From: peter.murysh...@zv.fraunhofer.de  
Sent: 29 April 2019 14:00
To: users@cloudstack.apache.org
Subject: AW: Troubleshooting the Exception "Unable to start VM instance"

Hi, Rakesh,

thanks!

After further digging the logs so far I can find:

Destroying vm VM[User|i-291-77209-VM] as it failed to create on Host with 
Id:null VM state transitted from :Stopped to Error with event: 
OperationFailedToErrorvm's original host id: null new host id: null host id 
before state transition: null

Additionally, via the log ID I've found an error which contains some base64 
encoding but does not decode well i.e. base64 exits with an error and outputs 
something lengthy (2972 chars) looking like a Java stack trace but with random 
binary characters. 

Error: [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-92:ctx-0c7bb167 
job-1027206/job-1027210 ctx-74dde55e) (logid:2477aa66) Complete async 
job-1027210, jobStatus: FAILED, resultCode: 0, result: rO0ABXNyAC9jb20u.

What is readable in this "base64" output is (special characters replaced with 
hyphen or new line):

com.cloud.utils.exception.CloudRuntimeExceptionVMOI
csErrorCodexr-java.lang.RuntimeException-detailMessaget
Ljava/lang/String;[
xr-java.lang.Throwable-Lcauset-Ljava/lang/Throwable;L
stackTracet-[Ljava/lang/StackTraceElement;
L-suppressedExceptionst-Ljava/util/Lis

kind regards
Peter



Von: Rakesh Venkatesh [www.rakeshv@gmail.com]
Gesendet: Montag, 29. April 2019 13:17
An: users@cloudstack.apache.org
Betreff: Re: Troubleshooting the Exception "Unable to start VM instance"

Hello Peter

If you dig into logs a little bit more, you can see the actual reason for the 
error. The usual errors are insufficient server capacity exception like not 
enough cpu, memory, ip address or mismatch between template tag and host tag or 
some other mismatch in the tags. These are the common errors I have seen.
Search for "startVirtualMachine" api and trace its jobid which is usually like 
"context-" and look at the logs

On Mon, Apr 29, 2019 at 12:58 PM  wrote:

> Hi, all,
>
> sometimes the system can't start a VM instance (a 530 error).
> In the logs there is the following trace - how to troubleshoot it and 
> understand which circumstances lead to it?
>
>
> com.cloud.utils.exception.CloudRuntimeException: Unable to start VM 
> instance
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4889)
> at sun.reflect.GeneratedMethodAccessor433.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5047)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:615)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:563)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> kind regards
> Peter
>
>

--
Thanks and regards
Rakesh venkatesh

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: Problem with ACS 4.11.2 and vCenter server

[Paul Angus]

Ah. vCenter 6.7 isn't supported yet, cloudstack won't recognise it.

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


-Original Message-
From: Florent Paillot  
Sent: 15 April 2019 14:26
To: users 
Subject: Re: Problem with ACS 4.11.2 and vCenter server

Hi Suresh,
The vCenter is a 6.7u2 (last build).

There is no issue log, that the problem... I don't see any error message 
concerning a failed connection to the vCenter and CS does not seems to send any 
packet to the vCenter.

Florent


- Mail original -
> De: "Suresh Kumar Anaparti" 
> À: "users" 
> Envoyé: Lundi 15 Avril 2019 15:10:44
> Objet: Re: Problem with ACS 4.11.2 and vCenter server

> Hi Florent,
> 
> Can you share the vCenter version and build details. Also, the 
> cloudstack management server log with the issue logs while connecting to 
> vCenter.
> 
> - Suresh
> 
> On Mon, Apr 15, 2019 at 6:24 PM Paul Angus  wrote:
> 
>> Assuming that you have updated the core code to recognise and use 'newer'
>> libraries/SDKs than the ones currently in use (and thoroughly tested 
>> it) then, please do create a pull request.  Otherwise, I personally 
>> would advise that you leave things 'as-is' to get the most stable experience.
>>
>> I don't *think* that you need to run
>>
>> mvn clean
>> mvn install -Dnoredist
>>
>> *After* installing the non-oss components.
>>
>> You might want to do a mvn clean before you start.
>>
>> It's been a while since I've done it manually now.
>>
>>
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>>
>>
>>
>>
>> -Original Message-
>> From: Florent Paillot 
>> Sent: 15 April 2019 13:17
>> To: users 
>> Subject: Re: Problem with ACS 4.11.2 and vCenter server
>>
>> Yes, this is the list of the files in deps/ :
>> cloud-iControl.jar  cloud-netscaler-sdx.jar  iControl-12.1.0.jar
>> install-non-oss.sh  manageontap.jar  vim25_51.jar  vim25_55.jar
>> vim25_60.jar  vim25_65.jar  vim25_67.jar
>>
>>
>> I had to add the following lines to "install-non-oss.sh" to get the build
>> pass :
>>
>> mvn install:install-file -Dfile=vim25_67.jar
>> -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25-Dversion=6.7
>>  -Dpackaging=jar
>> mvn install:install-file -Dfile=iControl-12.1.0.jar
>>  -DgroupId=com.cloud.com.f5 -DartifactId=icontrol
>> -Dversion=12.1  -Dpackaging=jar
>>
>> I can open a PR or an issue if it makes sense.
>>
>> Florent
>>
>> --
>> Florent PAILLOT
>> SESI - Cellule architecture
>>
>> INRIA Bordeaux -Sud-Ouest
>> 05.24.57.41.25
>>
>> - Mail original -
>> > De: "Paul Angus" 
>> > À: "users" 
>> > Envoyé: Lundi 15 Avril 2019 14:10:21
>> > Objet: RE: Problem with ACS 4.11.2 and vCenter server
>>
>> > When packaging, did you install all of the nonoss libraries  into the
>> > build before packaging?  including vmware-vim25-6.5.jar
>> >
>> > paul.an...@shapeblue.com
>> > www.shapeblue.com
>> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>> >
>> >
>> >
>> >
>> > -Original Message-
>> > From: Dag Sonstebo 
>> > Sent: 15 April 2019 12:43
>> > To: users@cloudstack.apache.org
>> > Subject: Re: Problem with ACS 4.11.2 and vCenter server
>> >
>> > Florent,
>> >
>> > Not aware of any issues but I'm no packaging expert so will let others
>> > respond to this.
>> >
>> > However - any reason you're not just using the RPM repositories rather
>> > than packaging yourself?
>> >
>> > Regards,
>> > Dag Sonstebo
>> > Cloud Architect
>> > ShapeBlue
>> >
>> >
>> >On 15/04/2019, 11:46, "Florent Paillot" 
>> wrote:
>> >
>> >Hi everyone,
>> >We have a problem with our test environment running ACS 4.11.2 on
>> CentOS 7, not
>> >communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and
>> CentOS 6 o
>> >CentOS 7). We have no problems with our KVM host.
>> >Our production is using 4.9.3 o, Centos 6 and everything is OK.
>> >
>> >I used tcpdump and see nothing going out from the management server
>> to the
>> >vCenter or the ESXi host.
>> >
>> >Could it be a package building problem or a vmware module loading?
>> >
>> >I used the following commands to build the packages :
>> >install-non-oss.sh
>> >mvn clean
>> >mvn install -Dnoredist
>> >package.sh -p noredist -d centos7
>> >
>> >
>> >On the production server I see a :
>> >
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
>> >file.
>> >I can't find it on the test environnement, is it linked to jetty ?
>> >
>> >Any help is welcome :)
>> >Regards,
>> >
>> >
>> >
>> >
>> >
>> > dag.sonst...@shapeblue.com
>> > www.shapeblue.com
>> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue

RE: Problem with ACS 4.11.2 and vCenter server

[Paul Angus]

As Suresh said, we'd need to see the management server logs to see whats 
happening.  I assume that your esxi hosts show as disconnected or alert?

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


-Original Message-
From: Florent Paillot  
Sent: 15 April 2019 14:17
To: users 
Subject: Re: Problem with ACS 4.11.2 and vCenter server

I just made a try with the shapeblue packages.

I can't see any change, still no traffic between the CS controller and the 
vCenter.


Florent

- Mail original -
> De: "Paul Angus" 
> À: "users" 
> Envoyé: Lundi 15 Avril 2019 14:54:40
> Objet: RE: Problem with ACS 4.11.2 and vCenter server

> Assuming that you have updated the core code to recognise and use 'newer'
> libraries/SDKs than the ones currently in use (and thoroughly tested 
> it) then, please do create a pull request.  Otherwise, I personally 
> would advise that you leave things 'as-is' to get the most stable experience.
> 
> I don't *think* that you need to run
> 
> mvn clean
> mvn install -Dnoredist
> 
> *After* installing the non-oss components.
> 
> You might want to do a mvn clean before you start.
> 
> It's been a while since I've done it manually now.
> 
> 
> 
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>  
> 
> 
> 
> -Original Message-
> From: Florent Paillot 
> Sent: 15 April 2019 13:17
> To: users 
> Subject: Re: Problem with ACS 4.11.2 and vCenter server
> 
> Yes, this is the list of the files in deps/ :
> cloud-iControl.jar  cloud-netscaler-sdx.jar  iControl-12.1.0.jar 
> install-non-oss.sh  manageontap.jar  vim25_51.jar  vim25_55.jar  
> vim25_60.jar vim25_65.jar  vim25_67.jar
> 
> 
> I had to add the following lines to "install-non-oss.sh" to get the build 
> pass :
> 
> mvn install:install-file -Dfile=vim25_67.jar 
> -DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25
> -Dversion=6.7   -Dpackaging=jar
> mvn install:install-file -Dfile=iControl-12.1.0.jar
> -DgroupId=com.cloud.com.f5 -DartifactId=icontrol-Dversion=12.1
> -Dpackaging=jar
> 
> I can open a PR or an issue if it makes sense.
> 
> Florent
> 
> --
> Florent PAILLOT
> SESI - Cellule architecture
> 
> INRIA Bordeaux -Sud-Ouest
> 05.24.57.41.25
> 
> - Mail original -
>> De: "Paul Angus" 
>> À: "users" 
>> Envoyé: Lundi 15 Avril 2019 14:10:21
>> Objet: RE: Problem with ACS 4.11.2 and vCenter server
> 
>> When packaging, did you install all of the nonoss libraries  into the 
>> build before packaging?  including vmware-vim25-6.5.jar
>> 
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>>  
>> 
>> 
>> 
>> -Original Message-
>> From: Dag Sonstebo 
>> Sent: 15 April 2019 12:43
>> To: users@cloudstack.apache.org
>> Subject: Re: Problem with ACS 4.11.2 and vCenter server
>> 
>> Florent,
>> 
>> Not aware of any issues but I'm no packaging expert so will let 
>> others respond to this.
>> 
>> However - any reason you're not just using the RPM repositories 
>> rather than packaging yourself?
>> 
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>> 
>> 
>>On 15/04/2019, 11:46, "Florent Paillot"  wrote:
>> 
>>Hi everyone,
>>We have a problem with our test environment running ACS 4.11.2 on CentOS 
>> 7, not
>>communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and CentOS 6 o
>>CentOS 7). We have no problems with our KVM host.
>>Our production is using 4.9.3 o, Centos 6 and everything is OK.
>>
>>I used tcpdump and see nothing going out from the management server to the
>>vCenter or the ESXi host.
>>
>>Could it be a package building problem or a vmware module loading?
>>
>>I used the following commands to build the packages :
>>install-non-oss.sh
>>mvn clean
>>mvn install -Dnoredist
>>package.sh -p noredist -d centos7
>>
>>
>>On the production server I see a :
>>
>> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
>>file.
>>I can't find it on the test environnement, is it linked to jetty ?
>>
>>Any help is welcome :)
>>Regards,
>>
>>
>>
>> 
>> 
>> dag.sonst...@shapeblue.com
>> www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue

RE: Problem with ACS 4.11.2 and vCenter server

[Paul Angus]

Assuming that you have updated the core code to recognise and use 'newer' 
libraries/SDKs than the ones currently in use (and thoroughly tested it) then, 
please do create a pull request.  Otherwise, I personally would advise that you 
leave things 'as-is' to get the most stable experience.

I don't *think* that you need to run

mvn clean
mvn install -Dnoredist

*After* installing the non-oss components.

You might want to do a mvn clean before you start.

It's been a while since I've done it manually now.



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


-Original Message-
From: Florent Paillot  
Sent: 15 April 2019 13:17
To: users 
Subject: Re: Problem with ACS 4.11.2 and vCenter server

Yes, this is the list of the files in deps/ :
cloud-iControl.jar  cloud-netscaler-sdx.jar  iControl-12.1.0.jar  
install-non-oss.sh  manageontap.jar  vim25_51.jar  vim25_55.jar  vim25_60.jar  
vim25_65.jar  vim25_67.jar


I had to add the following lines to "install-non-oss.sh" to get the build pass :

mvn install:install-file -Dfile=vim25_67.jar
-DgroupId=com.cloud.com.vmware -DartifactId=vmware-vim25-Dversion=6.7   
-Dpackaging=jar
mvn install:install-file -Dfile=iControl-12.1.0.jar 
-DgroupId=com.cloud.com.f5 -DartifactId=icontrol-Dversion=12.1  
-Dpackaging=jar

I can open a PR or an issue if it makes sense.

Florent

--
Florent PAILLOT
SESI - Cellule architecture

INRIA Bordeaux -Sud-Ouest
05.24.57.41.25

- Mail original -----
> De: "Paul Angus" 
> À: "users" 
> Envoyé: Lundi 15 Avril 2019 14:10:21
> Objet: RE: Problem with ACS 4.11.2 and vCenter server

> When packaging, did you install all of the nonoss libraries  into the 
> build before packaging?  including vmware-vim25-6.5.jar
> 
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>  
> 
> 
> 
> -Original Message-
> From: Dag Sonstebo 
> Sent: 15 April 2019 12:43
> To: users@cloudstack.apache.org
> Subject: Re: Problem with ACS 4.11.2 and vCenter server
> 
> Florent,
> 
> Not aware of any issues but I'm no packaging expert so will let others 
> respond to this.
> 
> However - any reason you're not just using the RPM repositories rather 
> than packaging yourself?
> 
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> 
> 
>On 15/04/2019, 11:46, "Florent Paillot"  wrote:
> 
>Hi everyone,
>We have a problem with our test environment running ACS 4.11.2 on CentOS 
> 7, not
>communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and CentOS 6 o
>CentOS 7). We have no problems with our KVM host.
>Our production is using 4.9.3 o, Centos 6 and everything is OK.
>
>I used tcpdump and see nothing going out from the management server to the
>vCenter or the ESXi host.
>
>Could it be a package building problem or a vmware module loading?
>
>I used the following commands to build the packages :
>install-non-oss.sh
>mvn clean
>mvn install -Dnoredist
>package.sh -p noredist -d centos7
>
>
>On the production server I see a :
>
> /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
>file.
>I can't find it on the test environnement, is it linked to jetty ?
>
>Any help is welcome :)
>Regards,
>
>
>
> 
> 
> dag.sonst...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue

RE: Problem with ACS 4.11.2 and vCenter server

[Paul Angus]

When packaging, did you install all of the nonoss libraries  into the build 
before packaging?  including vmware-vim25-6.5.jar

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


-Original Message-
From: Dag Sonstebo  
Sent: 15 April 2019 12:43
To: users@cloudstack.apache.org
Subject: Re: Problem with ACS 4.11.2 and vCenter server

Florent,

Not aware of any issues but I'm no packaging expert so will let others respond 
to this.

However - any reason you're not just using the RPM repositories rather than 
packaging yourself? 

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
 

On 15/04/2019, 11:46, "Florent Paillot"  wrote:

Hi everyone, 
We have a problem with our test environment running ACS 4.11.2 on CentOS 7, 
not communicating with a vCenter (upgraded from 4.9.3 to 4.11.2 and CentOS 6 o 
CentOS 7). We have no problems with our KVM host. 
Our production is using 4.9.3 o, Centos 6 and everything is OK. 

I used tcpdump and see nothing going out from the management server to the 
vCenter or the ESXi host. 

Could it be a package building problem or a vmware module loading? 

I used the following commands to build the packages : 
install-non-oss.sh 
mvn clean 
mvn install -Dnoredist 
package.sh -p noredist -d centos7 


On the production server I see a : 
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib/vmware-vim25-6.0.jar
 file. 
I can't find it on the test environnement, is it linked to jetty ? 

Any help is welcome :) 
Regards, 





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

cloudstack.org code website refactor

[Paul Angus]

Guys,

I've created a PR to fix the code on the website.  I haven't changed the 
content other than merging "Project Announcements" and "Latest Announcement" 
sections to save space.
This PR is only meant to be a base for any other content changes to be made 
from.

Refactor ( content unchanged )

  *   fix twitter feed; twitter have made custom feeds require oauth for api1.1 
- this uses public widget which only shows 
@cloudstack tweets, which does not require oauth
  *   "who we are" formatting is fixed
  *   "Announcements" from cloudstack atom feed rewritten as was broken
  *   The 'events' are pulled from a raw csv file in github 
(https://raw.githubusercontent.com/apache/cloudstack-www/master/data/acs-events.csv)
 Therefore THE SITE DOES NOT NEED TO BE REBUILT for upcoming events to be 
changed.

This refactor can CURRENTLY be reviewed at https://acs-www.shapeblue.com/www/
Kind regards

Paul.

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

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

[Paul Angus]

Hi Simon,

We're actually looking at it too right now.
The problem seems to be here:

https://github.com/apache/cloudstack/blob/4.11/scripts/vm/hypervisor/kvm/patchviasocket.py#L56-L59
s = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
s.connect(sock_file)
s.sendall(msg)
s.close()

Rohit can send commands manually, but through the script nothing gets sent.

*I* think that there should be something like:

data = s.recv(1024)
s.close()

to wait for the empty string to come back.

But I need Rohit to confirm it, otherwise a sleep(5) in there works but is very 
nasty...








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


-Original Message-
From: Simon Weller  
Sent: 12 April 2019 15:59
To: dev ; users 
Subject: Latest Qemu KVM EV appears to be broken with ACS

All,

After troubleshooting a strange issue with a new lab environment yesterday, it 
appears that the patchviasocket functionality we rely on for key and ip 
injection into our router/SSVM/CPVM images is broken with 
qemu-kvm-ev-2.12.0-18.el7 (January 2019 release). This was tested on Centos 7.6.
No data is injected and this was confirmed using socat on /dev/vport0p1. 
qemu-kvm-ev-2.10.0-21.el7_5.7.1 works, so hopefully this will save someone some 
pain and suffering trying to figure out why the deployed seems broken.

We're going to dig in and see if can figure out the patches responsible for it 
breaking.

-Si

RE: committer with merge rights on cloudstack-www

[Paul Angus]

Hi Peter,

No you don't need to be a committer to work with Marvin.  Andrija's reply was 
to the original question from Swen.

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


-Original Message-
From: peter.murysh...@zv.fraunhofer.de  
Sent: 11 April 2019 12:10
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi, Andrija and Paul,

so what I have understood, not only to be able to merge, but also just to get 
started with Marvin the test framework, I need to have an ASF (Apache Software 
Foundation) ID that is @apache.org email address?

Here I read:

"If your work shows merit, the PMC for the project may hold a vote to invite 
you to become a committer."
https://www.apache.org/foundation/getinvolved.html 

Well.. any ideas how to use Marvin then?

kind regards
Peter

Von: Andrija Panic [andrija.pa...@shapeblue.com]
Gesendet: Donnerstag, 11. April 2019 12:11
An: users@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

Is the following (what I did actually) enough ?

1.  Go to ASF ID, and add your github username(s): https://id.apache.org
2.  Go to Github settings and enable 2FA (two-factor authentication, I use 
google authenticator)
3.  Go to gitbox setup page: https://gitbox.apache.org/setup/

Once you've done #1-3, it may take upto an hour for the gitbox/asf scripts to 
kick and add your github account to the apache Github org and allow 
committer/access to cloudstack related repository.

Cheers

andrija.pa...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue




-Original Message-----
From: Paul Angus 
Sent: 11 April 2019 10:06
To: users@cloudstack.apache.org
Subject: RE: committer with merge rights on cloudstack-www

AH, it looks like 'we' have not noticed "the forest for the trees!"

There is a miniscule amount about the subject here.
http://cloudstack.apache.org/about.html

I'll action myself to write up some kind of explanation...



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




-Original Message-
From: peter.murysh...@zv.fraunhofer.de 
Sent: 11 April 2019 08:44
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi, Paul,

thanks for the addon with the Gitbox link. From the Gitbox guides I understand 
I have to go through some ASF registration, even election process? Seems to be 
not very straightforward.

Please help.

kind regards
Peter

____
Von: Paul Angus [paul.an...@shapeblue.com]
Gesendet: Mittwoch, 10. April 2019 18:36
An: users@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

I should have included a link:
https://gitbox.apache.org/setup/


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




-Original Message-----
From: Paul Angus 
Sent: 10 April 2019 16:57
To: users@cloudstack.apache.org
Subject: RE: committer with merge rights on cloudstack-www

Have you gone through the Apache GitBox account linking + 2FA malarkey?


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




-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 16:45
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi Paul,

as far as I understand I am unable to provide the whole workflow after creating 
a PR. After opening a PR which then get approved I cannot do the merge, the 
build and the upload to the asf-site branch (as mentioned in the README) 
because of missing privileges. To do that I need someone else's help with the 
right ones. So this ends up in a situation that a PR (#56) that I opened 5 days 
ago for updating only events on the main site has been approved, closed and 
merged, but not build and uploaded to the live page. Please tell me if there is 
something wrong in my workflow and how I get the new events on the live page.

cu Swen

-Ursprüngliche Nachricht-
Von: Paul Angus 
Gesendet: Mittwoch, 10. April 2019 16:13
An: users@cloudstack.apache.org; d...@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

Hi Swen,

We generally apply a more relaxed version of our commit into apache/cloudstack 
procedure for both docs and www.  AFAIR the same commit rights apply to 
cloudstack-www as cloudstack.
You should create a PR which at least one other person should review, which can 
then be merged.  Changing anything substantial about the website's look/feel is 
always going to escalate into a bit of a bike shedding exercise.

If you are planning on making substantial changes, advice would be to create a 
PR which can be reviewed and let everyone know, anyone interest

RE: committer with merge rights on cloudstack-www

[Paul Angus]

AH, it looks like 'we' have not noticed "the forest for the trees!"

There is a miniscule amount about the subject here.
http://cloudstack.apache.org/about.html

I'll action myself to write up some kind of explanation...



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


-Original Message-
From: peter.murysh...@zv.fraunhofer.de  
Sent: 11 April 2019 08:44
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi, Paul,

thanks for the addon with the Gitbox link. From the Gitbox guides I understand 
I have to go through some ASF registration, even election process? Seems to be 
not very straightforward.

Please help.

kind regards
Peter


Von: Paul Angus [paul.an...@shapeblue.com]
Gesendet: Mittwoch, 10. April 2019 18:36
An: users@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

I should have included a link:
https://gitbox.apache.org/setup/


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




-Original Message-----
From: Paul Angus 
Sent: 10 April 2019 16:57
To: users@cloudstack.apache.org
Subject: RE: committer with merge rights on cloudstack-www

Have you gone through the Apache GitBox account linking + 2FA malarkey?


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




-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 16:45
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi Paul,

as far as I understand I am unable to provide the whole workflow after creating 
a PR. After opening a PR which then get approved I cannot do the merge, the 
build and the upload to the asf-site branch (as mentioned in the README) 
because of missing privileges. To do that I need someone else's help with the 
right ones. So this ends up in a situation that a PR (#56) that I opened 5 days 
ago for updating only events on the main site has been approved, closed and 
merged, but not build and uploaded to the live page. Please tell me if there is 
something wrong in my workflow and how I get the new events on the live page.

cu Swen

-Ursprüngliche Nachricht-
Von: Paul Angus 
Gesendet: Mittwoch, 10. April 2019 16:13
An: users@cloudstack.apache.org; d...@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

Hi Swen,

We generally apply a more relaxed version of our commit into apache/cloudstack 
procedure for both docs and www.  AFAIR the same commit rights apply to 
cloudstack-www as cloudstack.
You should create a PR which at least one other person should review, which can 
then be merged.  Changing anything substantial about the website's look/feel is 
always going to escalate into a bit of a bike shedding exercise.

If you are planning on making substantial changes, advice would be to create a 
PR which can be reviewed and let everyone know, anyone interested will go and 
look.


On a linked note, I found this week that middleman v4 isn't compatible with how 
we have set up our source.  Some file extensions need changing, until that's 
done we wont be able to see what else (if anything) is broken.  I haven't 
gotten round to creating a PR to fix it, but it would be a bit redundant if 
things are potentially getting changed anyway.

Paul.


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




-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 14:22
To: users@cloudstack.apache.org
Subject: committer with merge rights on cloudstack-www

Dear community,

I want to get more involved in the great CloudStack community than only by this 
list. What I am looking for is to get our public page more informative and 
up-to-date from a content point of view. If you are want to get involved in 
CloudStack and are hitting the official page it looks kind of outdated and/or 
not maintained. I want to take care of this. Therefore I need merge privileges 
on the page repo on github and I ask kindly if this is ok for the community.

cu Swen

RE: committer with merge rights on cloudstack-www

[Paul Angus]

I should have included a link:
https://gitbox.apache.org/setup/


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


-Original Message-
From: Paul Angus  
Sent: 10 April 2019 16:57
To: users@cloudstack.apache.org
Subject: RE: committer with merge rights on cloudstack-www

Have you gone through the Apache GitBox account linking + 2FA malarkey?


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


-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 16:45
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi Paul,

as far as I understand I am unable to provide the whole workflow after creating 
a PR. After opening a PR which then get approved I cannot do the merge, the 
build and the upload to the asf-site branch (as mentioned in the README) 
because of missing privileges. To do that I need someone else's help with the 
right ones. So this ends up in a situation that a PR (#56) that I opened 5 days 
ago for updating only events on the main site has been approved, closed and 
merged, but not build and uploaded to the live page. Please tell me if there is 
something wrong in my workflow and how I get the new events on the live page.

cu Swen

-Ursprüngliche Nachricht-
Von: Paul Angus 
Gesendet: Mittwoch, 10. April 2019 16:13
An: users@cloudstack.apache.org; d...@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

Hi Swen,

We generally apply a more relaxed version of our commit into apache/cloudstack 
procedure for both docs and www.  AFAIR the same commit rights apply to 
cloudstack-www as cloudstack. 
You should create a PR which at least one other person should review, which can 
then be merged.  Changing anything substantial about the website's look/feel is 
always going to escalate into a bit of a bike shedding exercise.

If you are planning on making substantial changes, advice would be to create a 
PR which can be reviewed and let everyone know, anyone interested will go and 
look.


On a linked note, I found this week that middleman v4 isn't compatible with how 
we have set up our source.  Some file extensions need changing, until that's 
done we wont be able to see what else (if anything) is broken.  I haven't 
gotten round to creating a PR to fix it, but it would be a bit redundant if 
things are potentially getting changed anyway.

Paul.


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


-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 14:22
To: users@cloudstack.apache.org
Subject: committer with merge rights on cloudstack-www

Dear community,

I want to get more involved in the great CloudStack community than only by this 
list. What I am looking for is to get our public page more informative and 
up-to-date from a content point of view. If you are want to get involved in 
CloudStack and are hitting the official page it looks kind of outdated and/or 
not maintained. I want to take care of this. Therefore I need merge privileges 
on the page repo on github and I ask kindly if this is ok for the community.

cu Swen

RE: committer with merge rights on cloudstack-www

[Paul Angus]

Have you gone through the Apache GitBox account linking + 2FA malarkey?


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


-Original Message-
From: Swen - swen.io  
Sent: 10 April 2019 16:45
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi Paul,

as far as I understand I am unable to provide the whole workflow after creating 
a PR. After opening a PR which then get approved I cannot do the merge, the 
build and the upload to the asf-site branch (as mentioned in the README) 
because of missing privileges. To do that I need someone else's help with the 
right ones. So this ends up in a situation that a PR (#56) that I opened 5 days 
ago for updating only events on the main site has been approved, closed and 
merged, but not build and uploaded to the live page. Please tell me if there is 
something wrong in my workflow and how I get the new events on the live page.

cu Swen

-Ursprüngliche Nachricht-
Von: Paul Angus  
Gesendet: Mittwoch, 10. April 2019 16:13
An: users@cloudstack.apache.org; d...@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

Hi Swen,

We generally apply a more relaxed version of our commit into apache/cloudstack 
procedure for both docs and www.  AFAIR the same commit rights apply to 
cloudstack-www as cloudstack. 
You should create a PR which at least one other person should review, which can 
then be merged.  Changing anything substantial about the website's look/feel is 
always going to escalate into a bit of a bike shedding exercise.

If you are planning on making substantial changes, advice would be to create a 
PR which can be reviewed and let everyone know, anyone interested will go and 
look.


On a linked note, I found this week that middleman v4 isn't compatible with how 
we have set up our source.  Some file extensions need changing, until that's 
done we wont be able to see what else (if anything) is broken.  I haven't 
gotten round to creating a PR to fix it, but it would be a bit redundant if 
things are potentially getting changed anyway.

Paul.


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


-Original Message-
From: Swen - swen.io 
Sent: 10 April 2019 14:22
To: users@cloudstack.apache.org
Subject: committer with merge rights on cloudstack-www

Dear community,

I want to get more involved in the great CloudStack community than only by this 
list. What I am looking for is to get our public page more informative and 
up-to-date from a content point of view. If you are want to get involved in 
CloudStack and are hitting the official page it looks kind of outdated and/or 
not maintained. I want to take care of this. Therefore I need merge privileges 
on the page repo on github and I ask kindly if this is ok for the community.

cu Swen

RE: committer with merge rights on cloudstack-www

[Paul Angus]

Hi Swen,

We generally apply a more relaxed version of our commit into apache/cloudstack 
procedure for both docs and www.  AFAIR the same commit rights apply to 
cloudstack-www as cloudstack. 
You should create a PR which at least one other person should review, which can 
then be merged.  Changing anything substantial about the website's look/feel is 
always going to escalate into a bit of a bike shedding exercise.

If you are planning on making substantial changes, advice would be to create a 
PR which can be reviewed and let everyone know, anyone interested will go and 
look.


On a linked note, I found this week that middleman v4 isn't compatible with how 
we have set up our source.  Some file extensions need changing, until that's 
done we wont be able to see what else (if anything) is broken.  I haven't 
gotten round to creating a PR to fix it, but it would be a bit redundant if 
things are potentially getting changed anyway.

Paul.


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


-Original Message-
From: Swen - swen.io  
Sent: 10 April 2019 14:22
To: users@cloudstack.apache.org
Subject: committer with merge rights on cloudstack-www

Dear community,

I want to get more involved in the great CloudStack community than only by this 
list. What I am looking for is to get our public page more informative and 
up-to-date from a content point of view. If you are want to get involved in 
CloudStack and are hitting the official page it looks kind of outdated and/or 
not maintained. I want to take care of this. Therefore I need merge privileges 
on the page repo on github and I ask kindly if this is ok for the community.

cu Swen

RE: NetScaler-Related API Functions missing, causing Session Expired

[Paul Angus]

Have you migrated to dynamic roles yet?  The old commands.properties file has 
been deprecated.
Assuming that you haven't customised your commands.properties file, you should 
run the migration script using the 'install default roles' switch ( -D ).

http://docs.cloudstack.apache.org/en/4.11.2.0/adminguide/accounts.html#using-dynamic-roles


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


-Original Message-
From: Richard Lawley  
Sent: 29 March 2019 12:29
To: users@cloudstack.apache.org
Subject: NetScaler-Related API Functions missing, causing Session Expired

I've recently upgraded a couple of installations from 4.8 to 4.11.2.
Since the upgrade, I am unable to perform certain operations, such as adding a 
Network Offering, via the UI.  This shows up as getting a Session Expired 
message, and kicking me out.  I've checked the underlying requests, and it 
seems that the following API calls all return 401 (verified with CMK):

* listRegisteredServicePackages (used when going to Add Network Offering)
* listNetscalerControlCenter (used when viewing Netscaler Element in Network 
Service Providers)

We don't use Netscaler, but it seems that something is preventing us from 
accessing those APIs (using admin user), which is preventing us from adding a 
network offering.

The Management server contains the log entry:
The given command 'listNetscalerControlCenter' either does not exist, is not 
available for user, or not available from ip address '/x.x.x.x'.

Possibly also related, I've noticed that after running "cmk sync" it discovers 
567 APIs, but on a clean install in my test lab it discovers 590.

Any suggestions for how these APIs might be being made unavailable?

Regards,
Richard

[MESSAGE] Self-Introductory Message

[Paul Angus]

Hi Everyone,



Well it is official now, for the next year I'll be the Chairman/VP of the
Apache CloudStack Project.  To dive straight into the clichés; for me it is
an honour and a privilege to hold this position.



There are so many awesome people doing awesome things in this CloudStack
community. And there are also many people that I meet that, although can’t
say so due to their company policies, genuinely appreciate what everyone
does.



I have no big technical agenda that I wish to push during my tenure. I
would just like to try to bottle the sense of camaraderie and family that I
feel whenever I'm at a CloudStack Collaboration Conference and bring that
to the community as a whole; throughout the year.



I would like to try to bring closer together the 'users' and the
'developers' in the community.  I think that the 'developers' can benefit
from users' insights but also experience the positivity and excitement that
new helpful features generate, and 'users' can benefit from seeing how
tricky trying to develop features in a constantly shifting landscape is.



I will also try to encourage organisations which use CloudStack but don't
talk about it to get out and do so, I see it as an easy way for them to
protect their investment in CloudStack as its a virtual circle that will
lead to more organisations following suit, which in turn will bring even
more interest and participation in the project.



And finally... if nothing else, please excuse the use of English spelling.



Many thanks

Paul Angus
Chairman/VP of the Apache CloudStack Project

[MESSAGE] Self-Introductory Message

[Paul Angus]

Hi Everyone,



Well it is official now, for the next year I'll be the Chairman/VP of the
Apache CloudStack Project.  To dive straight into the clichés; for me it is
an honour and a privilege to hold this position.



There are so many awesome people doing awesome things in this CloudStack
community. And there are also many people that I meet that, although can’t
say so due to their company policies, genuinely appreciate what everyone
does.



I have no big technical agenda that I wish to push during my tenure. I
would just like to try to bottle the sense of camaraderie and family that I
feel whenever I'm at a CloudStack Collaboration Conference and bring that
to the community as a whole; throughout the year.



I would like to try to bring closer together the 'users' and the
'developers' in the community.  I think that the 'developers' can benefit
from users' insights but also experience the positivity and excitement that
new helpful features generate, and 'users' can benefit from seeing how
tricky trying to develop features in a constantly shifting landscape is.



I will also try to encourage organisations which use CloudStack but don't
talk about it to get out and do so, I see it as an easy way for them to
protect their investment in CloudStack as its a virtual circle that will
lead to more organisations following suit, which in turn will bring even
more interest and participation in the project.



And finally... if nothing else, please excuse the use of English spelling.



Many thanks

Paul Angus
Chairman/VP of the Apache CloudStack Project

RE: [ANNOUNCEMENT] Apache CloudStack CloudMonkey v6.0.0

[Paul Angus]

Great, Well done Rohit!

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


-Original Message-
From: Rohit Yadav  
Sent: 20 March 2019 12:13
To: d...@cloudstack.apache.org; users@cloudstack.apache.org; 
annou...@cloudstack.apache.org; market...@cloudstack.apache.org
Subject: [ANNOUNCEMENT] Apache CloudStack CloudMonkey v6.0.0

The Apache Software Foundation Announces Apache® CloudMonkey® v6.0.

Popular Open Source Command Line Interface tool that simplifies Apache 
CloudStack configuration and management now faster and easier to use.

Wakefield, MA, March 20, 2019 (GLOBE NEWSWIRE) -- The Apache Software 
Foundation (ASF), the all-volunteer developers, stewards, and incubators of 
more than 350 Open Source projects and initiatives, announced today Apache® 
CloudStack® CloudMonkey v6.0, the latest version of the turnkey enterprise 
Cloud orchestration platform's command line interface tool.

Apache CloudStack is the proven, highly scalable, and easy-to-deploy IaaS 
platform used for rapidly creating private, public, and hybrid Cloud 
environments. Thousands of large-scale public Cloud providers and enterprise 
organizations use Apache CloudStack to enable billions of dollars worth of 
business transactions annually across their clouds.

Apache CloudMonkey v6.0.0 is the latest major release since the previous major 
5.x release in September 2013. CloudMonkey v6.0.0 is a rewrite of the original 
tool in Go programming language, and can be used both as an interactive shell 
and as a command line tool that simplifies CloudStack configuration and 
management.

Some of the new features and major changes include:

- Rewrite in Go, ships as single binary for Linux, Mac, and Windows
- Drop-in replacement for legacy Python-based cloudmonkey
- About 5-20x faster than legacy Python-based cloudmonkey
- Interactive UX for parameter and arg completion and selection
- JSON is the default output format
- New column based output
- Enable debug mode using set debug true option, file-based logging removed
- Per server profile based API cache
- New syntax arg=@/path/to/file to pass the content of file as API argument 
value similar to curl
- Improve help docs using -h argument
- Removed: XML output, coloured output, several set options

"This release is the work of over one year of effort and driven by the people 
operating CloudStack clouds," said Rohit Yadav, Apache CloudStack CloudMonkey 
v6.0 author, and release manager. "I would like to thank the contributors 
across all of these organizations for supporting this release, which reflects 
both the user-driven nature of our community and the Apache CloudStack 
project's commitment to continue to be the most stable, easily deployable, 
scalable Open Source platform for IaaS. Along with ease of installation, usage 
and availability of cross-platform dependency-free builds including Windows 
builds, v6.0 brings many changes and optimizations such as more interactive 
shell for parameter completion, faster API requests processing, server profile 
specific API caching, improved API help docs and a new syntax to pass content 
of files as API parameter argument."
More on the background and story behind the CloudMonkey 6.0 effort can be found 
at https://blogs.apache.org/cloudstack/entry/what-s-coming-in-cloudmonkey

"Apache CloudStack is a significant part of our Cloud portfolio right now – we 
run large deployments all over the world, often supporting critical customer 
applications," said Robert van der Meulen, Product Strategy Lead at Leaseweb 
Global B.V. "CloudMonkey is an invaluable tool for interacting with 
CloudStack-based clouds, and it's the go-to tool that we recommend to our 
customers when they want to use command-line interaction with our CloudStack 
platforms."

"CloudMonkey is an effective tool for the operators of CloudStack environments 
and it becomes essential in large-scale CloudStack deployments," said Giles 
Sirett, CEO of ShapeBlue. "It's great to see this new version of CloudMonkey: 
having a CLI that can run on Windows desktops as well as Linux and Mac is 
important as we see more enterprise adoption of Apache CloudStack."

"CloudMonkey is now written in Golang, and with version v6.0 loading, speed has 
been drastically improved (accessing the CLI in under 0.5s)," said Pierre-Luc 
Dion, Cloud Architect at Cloud.ca. "This simplifies installation, deployments, 
updates, and operational efficiency."

"After many years of managing production Apache CloudStack deployments, I 
consider CloudMonkey a core tool in anyone's CloudStack toolkit, and now also 
being available for Windows makes me really happy," said Andrija Panic, Apache 
CloudStack Committer. "I can certainly see major speed improvements, but also 
having backward compatibility is what is so great with this new release."

Catch Apache CloudStack in action at ApacheCon 9-12 September 2019 in Las 
Vegas, Nevada, and at numerous 

RE: [RESULT][VOTE] Apache CloudStack 4.12.0.0

[Paul Angus]

Well done Gabriel,

Are you sorted to do the documentation or do you need some help?  I should have 
some time next week if you need a hand.

Kind regards

Paul.

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


-Original Message-
From: Gabriel Beims Bräscher  
Sent: 19 March 2019 21:37
To: dev ; users 
Subject: [RESULT][VOTE] Apache CloudStack 4.12.0.0

Hi all,

After 3 business days, the vote for CloudStack 4.12.0.0 *passes* with 4 PMC
+ 2 non-PMC votes.

+1 (PMC / binding)
* Wido den Hollander
* Simon Weller
* Rafael Weingärtner
* Rohit Yadav

+1 (nonbinding)
* Gabriel Bräscher
* Nicolas Vazquez

0
none

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours to give 
the mirrors time to catch up.

Best regards,
Gabriel

RE: Disaster after maintenance

[Paul Angus]

ed restarting, but it does not start.
>> >> >
>> >> >
>> >> > >> Do you have some NUMA constraints or anything which requires
>> >> particular
>> >> > RAM configuration?
>> >> > No
>> >> >
>> >> >  libvirtd.service - Virtualization daemon
>> >> >Loaded: loaded (/usr/lib/systemd/system/libvirtd.service;
>> >> > enabled; vendor preset: enabled)
>> >> >Active: failed (Result: start-limit) since Tue 2019-03-19
>> >> > 13:03:07
>> >> GMT;
>> >> > 12s ago
>> >> >  Docs: man:libvirtd(8)
>> >> >https://libvirt.org
>> >> >   Process: 892 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS
>> >> > (code=exited,
>> >> > status=1/FAILURE)
>> >> >  Main PID: 892 (code=exited, status=1/FAILURE)
>> >> > Tasks: 19 (limit: 32768)
>> >> >CGroup: /system.slice/libvirtd.service
>> >> >├─11338 /usr/sbin/libvirtd -d -l
>> >> >├─11909 /usr/sbin/dnsmasq
>> >> > --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
>> >> > --dhcp-script=/usr/libexec/libvirt_leaseshelper
>> >> >└─11910 /usr/sbin/dnsmasq
>> >> > --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
>> >> > --dhcp-script=/usr/libexec/libvirt_leaseshelper
>> >> >
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Failed to
>> >> > start Virtualization daemon.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Unit
>> >> > libvirtd.service entered failed state.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]:
>> >> libvirtd.service
>> >> > failed.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]:
>> >> libvirtd.service
>> >> > holdoff time over, scheduling restart.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Stopped
>> >> > Virtualization daemon.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: start
>> >> > request repeated too quickly for libvirtd.service Mar 19 13:03:07
>> >> > mtl1-apphst04.mt.pbt.com.mt systemd[1]: Failed to start
>> >> > Virtualization daemon.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Unit
>> >> > libvirtd.service entered failed state.
>> >> > Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]:
>> >> libvirtd.service
>> >> > failed.
>> >> >
>> >> >
>> >> > On Tue, Mar 19, 2019 at 3:04 PM Paul Angus
>> >> > 
>> >> > wrote:
>> >> >
>> >> > > Can you check that the cloudstack agent is running on the host
>> >> > > and the agent logs (usual logs directory) Also worth checking
>> >> > > that libvirt has started ok.  Do you have some
>> >> NUMA
>> >> > > constraints or anything which requires particular RAM
>> configuration?
>> >> > >
>> >> > > paul.an...@shapeblue.com
>> >> > > www.shapeblue.com
>> >> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > > -Original Message-
>> >> > > From: Jevgeni Zolotarjov 
>> >> > > Sent: 19 March 2019 14:49
>> >> > > To: users@cloudstack.apache.org
>> >> > > Subject: Re: Disaster after maintenance
>> >> > >
>> >> > > Can you try migrating a VM to the server that you changed the RAM
>> >> amount?
>> >> > >
>> >> > > Also:
>> >> > > What is the hypervisor version?
>> >> > > KVM
>> >> > > QEMU Version : 2.0.0
>> >> > > Release : 1.el7.6
>> >> > >
>> >> > >
>> >> > > Host status in ACS?
>> >> > > 1st server: Unsecure
>> >> > > 2nd server: Disconnected
>> >> > >
>> >> > > Did you try to force a VM to start/deploy in this server where you
>> >> > changed
>> >> > > the RAM?
>> >> >

RE: Disaster after maintenance

[Paul Angus]

Libvirtd has its own logs, so you'll need to look at those I'm afraid.

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


-Original Message-
From: Jevgeni Zolotarjov  
Sent: 19 March 2019 15:09
To: users@cloudstack.apache.org
Subject: Re: Disaster after maintenance

That's it - libvirtd failed to start on second host.
Tried restarting, but it does not start.


>> Do you have some NUMA constraints or anything which requires 
>> particular
RAM configuration?
No

 libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: start-limit) since Tue 2019-03-19 13:03:07 GMT; 12s 
ago
 Docs: man:libvirtd(8)
   https://libvirt.org
  Process: 892 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=exited,
status=1/FAILURE)
 Main PID: 892 (code=exited, status=1/FAILURE)
Tasks: 19 (limit: 32768)
   CGroup: /system.slice/libvirtd.service
   ├─11338 /usr/sbin/libvirtd -d -l
   ├─11909 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/libexec/libvirt_leaseshelper
   └─11910 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/libexec/libvirt_leaseshelper

Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Failed to start 
Virtualization daemon.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Unit libvirtd.service 
entered failed state.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: libvirtd.service failed.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: libvirtd.service 
holdoff time over, scheduling restart.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Stopped Virtualization 
daemon.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: start request repeated 
too quickly for libvirtd.service Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt 
systemd[1]: Failed to start Virtualization daemon.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: Unit libvirtd.service 
entered failed state.
Mar 19 13:03:07 mtl1-apphst04.mt.pbt.com.mt systemd[1]: libvirtd.service failed.


On Tue, Mar 19, 2019 at 3:04 PM Paul Angus  wrote:

> Can you check that the cloudstack agent is running on the host and the 
> agent logs (usual logs directory) Also worth checking that libvirt has 
> started ok.  Do you have some NUMA constraints or anything which 
> requires particular RAM configuration?
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Jevgeni Zolotarjov 
> Sent: 19 March 2019 14:49
> To: users@cloudstack.apache.org
> Subject: Re: Disaster after maintenance
>
> Can you try migrating a VM to the server that you changed the RAM amount?
>
> Also:
> What is the hypervisor version?
> KVM
> QEMU Version : 2.0.0
> Release : 1.el7.6
>
>
> Host status in ACS?
> 1st server: Unsecure
> 2nd server: Disconnected
>
> Did you try to force a VM to start/deploy in this server where you changed
> the RAM?
> Host status became disconnected. I don't know how to make it "connected"
> again
>
>
>
> On Tue, Mar 19, 2019 at 2:42 PM Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Can you try migrating a VM to the server that you changed the RAM amount?
> >
> > Also:
> > What is the hypervisor version?
> > Host status in ACS?
> > Did you try to force a VM to start/deploy in this server where you
> > changed the RAM?
> >
> >
> > On Tue, Mar 19, 2019 at 9:39 AM Jevgeni Zolotarjov
> >  > >
> > wrote:
> >
> > > We have Cloudstack 4.11.2 setup running fine for few months (>4) The
> > > setup is very simple: 2 hosts We decided to do a maintenance to
> > > increase RAM on both servers
> > >
> > > For this we put first server to maintenance. All VMS moved to second
> > > host after a while.
> > >
> > > Then first server was shutdown, RAM increased, server turned ON.
> > > Now nothing starts on first server.
> > >
> > >
> > > Tried to delete network, but this fails as well
> > >
> > > Please help !
> > >
> > > Here is extract from log:
> > > ==
> > > 2019-03-19 12:27:53,064 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
> > > (secstorage-1:ctx-16d6c797) (logid:7e3160ce) Zone 1 is ready to
> > > launch secondary storage VM
> > > 2019-03-19 12:27:53,125 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> > > (consoleproxy-1:ctx-cbd034b9) (logid:0

RE: Disaster after maintenance

[Paul Angus]

Can you check that the cloudstack agent is running on the host and the agent 
logs (usual logs directory)
Also worth checking that libvirt has started ok.  Do you have some NUMA 
constraints or anything which requires particular RAM configuration?

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


-Original Message-
From: Jevgeni Zolotarjov  
Sent: 19 March 2019 14:49
To: users@cloudstack.apache.org
Subject: Re: Disaster after maintenance

Can you try migrating a VM to the server that you changed the RAM amount?

Also:
What is the hypervisor version?
KVM
QEMU Version : 2.0.0
Release : 1.el7.6


Host status in ACS?
1st server: Unsecure
2nd server: Disconnected

Did you try to force a VM to start/deploy in this server where you changed the 
RAM?
Host status became disconnected. I don't know how to make it "connected"
again



On Tue, Mar 19, 2019 at 2:42 PM Rafael Weingärtner < 
rafaelweingart...@gmail.com> wrote:

> Can you try migrating a VM to the server that you changed the RAM amount?
>
> Also:
> What is the hypervisor version?
> Host status in ACS?
> Did you try to force a VM to start/deploy in this server where you 
> changed the RAM?
>
>
> On Tue, Mar 19, 2019 at 9:39 AM Jevgeni Zolotarjov 
>  >
> wrote:
>
> > We have Cloudstack 4.11.2 setup running fine for few months (>4) The 
> > setup is very simple: 2 hosts We decided to do a maintenance to 
> > increase RAM on both servers
> >
> > For this we put first server to maintenance. All VMS moved to second 
> > host after a while.
> >
> > Then first server was shutdown, RAM increased, server turned ON.
> > Now nothing starts on first server.
> >
> >
> > Tried to delete network, but this fails as well
> >
> > Please help !
> >
> > Here is extract from log:
> > ==
> > 2019-03-19 12:27:53,064 DEBUG [o.a.c.s.SecondaryStorageManagerImpl]
> > (secstorage-1:ctx-16d6c797) (logid:7e3160ce) Zone 1 is ready to 
> > launch secondary storage VM
> > 2019-03-19 12:27:53,125 DEBUG [c.c.c.ConsoleProxyManagerImpl]
> > (consoleproxy-1:ctx-cbd034b9) (logid:0a8c8bf4) Zone 1 is ready to 
> > launch console proxy
> > 2019-03-19 12:27:53,181 DEBUG [c.c.a.ApiServlet]
> > (qtp510113906-285:ctx-6c5e11c3) (logid:cd8e30be) ===START===
> 192.168.5.140
> > -- GET
> >
> >
> command=deleteNetwork=4ba834ed-48f3-468f-b667-9bb2d2c258f1
> =json&_=1552998473154
> > 2019-03-19 12:27:53,186 DEBUG [c.c.a.ApiServer]
> > (qtp510113906-285:ctx-6c5e11c3 ctx-0cc34dc6) (logid:cd8e30be) CIDRs 
> > from which account 
> > 'Acct[15863393-8e8d-11e7-8f52-f04da2002bbe-admin]' is
> allowed
> > to perform API calls: 0.0.0.0/0,::/0
> > 2019-03-19 12:27:53,208 INFO  [o.a.c.f.j.i.AsyncJobMonitor]
> > (API-Job-Executor-1:ctx-d4970c19 job-5081) (logid:f6751fa7) Add 
> > job-5081 into job monitoring
> > 2019-03-19 12:27:53,209 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (qtp510113906-285:ctx-6c5e11c3 ctx-0cc34dc6) (logid:cd8e30be) submit
> async
> > job-5081, details: AsyncJobVO {id:5081, userId: 2, accountId: 2,
> > instanceType: Network, instanceId: 204, cmd:
> > org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd, cmdInfo:
> >
> >
> {"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId
> ":"2615","id":"4ba834ed-48f3-468f-b667-9bb2d2c258f1","ctxDetails":"{\"
> interface
> >
> >
> com.cloud.network.Network\":\"4ba834ed-48f3-468f-b667-9bb2d2c258f1\"}"
> ,"ctxAccountId":"2","uuid":"4ba834ed-48f3-468f-b667-9bb2d2c258f1","cmd
> EventType":"NETWORK.DELETE","_":"1552998473154"},
> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> > result: null, initMsid: 264216221068220, completeMsid: null, lastUpdated:
> > null, lastPolled: null, created: null}
> > 2019-03-19 12:27:53,211 DEBUG [c.c.a.ApiServlet]
> > (qtp510113906-285:ctx-6c5e11c3 ctx-0cc34dc6) (logid:cd8e30be) 
> > ===END===
> > 192.168.5.140 -- GET
> >
> >
> command=deleteNetwork=4ba834ed-48f3-468f-b667-9bb2d2c258f1
> =json&_=1552998473154
> > 2019-03-19 12:27:53,212 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-1:ctx-d4970c19 job-5081) (logid:16897ea6) 
> > Executing AsyncJobVO {id:5081, userId: 2, accountId: 2, 
> > instanceType: Network,
> > instanceId: 204, cmd:
> > org.apache.cloudstack.api.command.user.network.DeleteNetworkCmd, cmdInfo:
> >
> >
> {"response":"json","ctxUserId":"2","httpmethod":"GET","ctxStartEventId
> ":"2615","id":"4ba834ed-48f3-468f-b667-9bb2d2c258f1","ctxDetails":"{\"
> interface
> >
> >
> com.cloud.network.Network\":\"4ba834ed-48f3-468f-b667-9bb2d2c258f1\"}"
> ,"ctxAccountId":"2","uuid":"4ba834ed-48f3-468f-b667-9bb2d2c258f1","cmd
> EventType":"NETWORK.DELETE","_":"1552998473154"},
> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> > result: null, initMsid: 264216221068220, completeMsid: null, lastUpdated:
> > null, lastPolled: null, created: null}
> > 2019-03-19 12:27:53,257 WARN  [o.a.c.e.o.NetworkOrchestrator]
> > 

Re: Cloudstack with vsphere and distributed vswitch deployment

[Paul Angus]

Hi Sergei,

If you look in the UI in the infrastructure tab and navigate through:

 Infrastructure > Zones > [YOUR_ZONE] > Physical Network > 
[NETWORK_WITH_MGMT_ON] > management.

what is the vmware traffic label?

It should be something like:

vSwitch0,6,vmwaresvs
NAME_OF_VSWITCH, VLAN ,  TYPE_OF_VSWITCH

the type vSwitch will be vmwaresvs or vmwaredvs


From: Sergei Hanus 
Sent: 14 March 2019 09:27
To: users@cloudstack.apache.org
Subject: Cloudstack with vsphere and distributed vswitch deployment

 Good day.

I have deployed Cludstack together with vsphere. After creating of first
zone I noticed, that Cloudstack is trying to deploy system vm, but
attempts is unsuccessful.

My management network is configured with standard switch. But in logs I
see, that service vm creation fails, because it cannot find distributed
vswitch named dvSwitch0, while in configuration it doesn't even mentionn
this distributed vswitch. I indeed do have distributed vswitch
configured, but it is named vm_dvs, and it is used only for guest
network, not management. This situation looks like a bug to me. Here is
the log I see:


  Processing:  { Ans: , MgmtId: 2886799893, via: 2(172.17.18.28), Ver:
v1, Flags: 110,
[{"com.cloud.agent.api.StartAnswer":{"vm":{"id":18,"name":"s-18-VM","bootloader":"HVM","state":"Starting","type":"SecondaryStorageVm","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"hostName":"s-18-VM","arch":"x86_64","os":"Other
Linux (64-bit)","bootArgs":" template=domP type=secstorage
host=localhost port=8250 name=s-18-VM zone=1 pod=1 guid=s-18-VM
workers=5
resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
instance=SecStorage sslcopy=false role=templateProcessor mtu=1500
eth2ip=10.255.255.52 eth2mask=255.255.255.0 gateway=10.255.255.1
public.network.device=eth2 eth0mask=0.0.0.0 eth0ip=0.0.0.0
eth1ip=172.17.18.34 eth1mask=255.255.255.0 localgw=172.17.18.1
private.network.device=eth1 internaldns1=172.17.17.11 dns1=172.17.17.11
nfsVersion=null","enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"OY8SHIPa6sZ0sM-E2xtjyA","params":{"vmware.reserve.cpu":"false","nicAdapter":"E1000","vmware.reserve.mem":"false"},"uuid":"7ec256e7-ab71-4875-b948-1ca29ad6aaca","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"18e502c3-2990-45e0-9444-53ea3934288d","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"fadaba61-7c07-3308-9fd3-780810ab2e86","id":1,"poolType":"VMFS","host":"VMFS
datastore:
/DC1/lab-vms","path":"/DC1/lab-vms","port":0,"url":"VMFS://VMFS
datastore:
/DC1/lab-vms/DC1/lab-vms/?ROLE=Primary=fadaba61-7c07-3308-9fd3-780810ab2e86","isManaged":false}},"name":"ROOT-18","size":0,"path":"ROOT-18_2","volumeId":18,"vmName":"s-18-VM","accountId":1,"format":"OVA","provisioningType":"THIN","id":18,"deviceId":0,"bytesReadRate":0,"bytesWriteRate":0,"iopsReadRate":0,"iopsWriteRate":0,"hypervisorType":"VMware"}},"diskSeq":0,"path":"ROOT-18_2","type":"ROOT","_details":{"storageHost":"VMFS
datastore:
/DC1/lab-vms","managed":"false","storagePort":"0","volumeSize":"0"}}],"nics":[{"deviceId":2,"networkRateMbps":-1,"defaultNic":true,"pxeDisable":true,"nicUuid":"e981f219-5e10-4770-85fb-6b25c97f2849","details":{"MacAddressChanges":"true","PromiscuousMode":"false","ForgedTransmits":"true"},"dpdkDisabled":false,"uuid":"b08c11ce-8e25-4772-8b55-dcdc42bd3193","ip":"10.255.255.52","netmask":"255.255.255.0","gateway":"10.255.255.1","mac":"1e:00:d2:00:00:38","dns1":"172.17.17.11","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://untagged","isolationUri":"vlan://untagged","isSecurityGroupEnabled":false},{"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":true,"nicUuid":"031ac70f-9350-4eac-a05c-8ea1ffd9cd0e","details":{"MacAddressChanges":"true","PromiscuousMode":"false","ForgedTransmits":"true"},"dpdkDisabled":false,"uuid":"6c37cab9-b5e6-4731-a8aa-75d50459e1c6","mac":"02:00:75:2d:00:12","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false,"*name":"vSwitch0,,vmwaresvs*"},{"deviceId":1,"networkRateMbps":-1,"defaultNic":false,"pxeDisable":true,"nicUuid":"32297819-967c-4f93-8ebf-ed4cc2372ba3","details":{"MacAddressChanges":"true","PromiscuousMode":"false","ForgedTransmits":"true"},"dpdkDisabled":false,"uuid":"97bb426a-7530-4ae1-9c8a-04cceabceeae","ip":"172.17.18.34","netmask":"255.255.255.0","gateway":"172.17.18.1","mac":"1e:00:2f:00:00:01","broadcastType":"Native","type":"Management","isSecurityGroupEnabled":false,"*name":"vSwitch0,,vmwaresvs"*}],"guestOsDetails":{},"extraConfig":{}},"result":false,"details":"StartCommand
failed due to Exception: java.lang.Exception\nMessage: *Unable to find
distributed vSwitch dvSwitch*0\n","wait":0}}] }

Could anybody, please, comment - how to further troubleshoot this situation?


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

RE: RHEL compatibility

[Paul Angus]

Hi Gary,

I do know of some guys running RHEL rather than CentOS, as I recall it's just a 
matter of making sure that the hosts have access to the right repos.

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


-Original Message-
From: Morrow, Gary G II CIV DISA JT (USA)  
Sent: 12 March 2019 19:50
To: users@cloudstack.apache.org
Subject: RHEL compatibility

Question for the group:  Is CloudStack compatible with RHEL?  I know it is 
similar to Centos but I didn't know if anyone had installed it on there?  

Respectfully,
Gary Morrow

RE: New* UI SVG hires icons for CloudStack (Vote)

[Paul Angus]

Hey Sven,

If the icons are separate files then it will be easy enough for people to 
swap-in a branded set.
I'm not up-to-date with the modern practices, but I assume that it's ok to move 
away from the single sprite file..


Nb scope-creep is when people keep adding little extras to the original scope 
until it turns into a monster.

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


-Original Message-
From: Sven Vogel  
Sent: 12 March 2019 11:22
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: Re: New* UI SVG hires icons for CloudStack (Vote)

@Paul

Maybe we don’t need this map anymore. We evaluate the things.

SVG will be separated files.

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 11.03.2019 um 19:02 schrieb Sven Vogel :
>
> Hi Paul,
>
>
> Thanks for the votes. Many users and devs want new icons. Okay let’s start.
>
> Sorry i saw your Post to late. Sure.  We will try to implement it.
>
> We want to make it easier to implement new icons.
>
> To your questions.
> Icons should also be greeted out or so you mean the complete button?
>
> We check how we can make it with svg so we have always sharp pictures. 
> :)
>
> What is scopescreep?
>
> Greetings
>
> Sven
>
>
>
> 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<https://blog.ewerk.com/> | 
> LinkedIn<https://www.linkedin.com/company/ewerk-group> | 
> Xing<https://www.xing.com/company/ewerk> | 
> Twitter<https://twitter.com/EWERK_Group> | 
> Facebook<https://de-de.facebook.com/EWERK.IT/>
>
> 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 06.03.2019 um 18:30 schrieb Paul Angus 
> mailto:paul.an...@shapeblue.com>>:
>
> This is a great idea,  I wonder, could you refactor the code/positions on the 
> sprite image to make dropping new icon sprites in generally easier?
> Maybe have them in a rows, such that there is always a specific offset for 
> 'greyed out', 'selected', 'mouse over' etc ?
> #scopecreep
>
>
> paul.an...@shapeblue.com<mailto:paul.an...@shapeblue.com>
> www.shapeblue.com<http://www.shapeblue.com>
> Amadeus Ho

RE: [VOTE] Release Apache CloudStack CloudMonkey 6.0.0

[Paul Angus]

Thanks Gregor, every vote counts !


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


-Original Message-
From: Riepl, Gregor (SWISS TXT)  
Sent: 12 March 2019 10:10
To: users@cloudstack.apache.org; d...@cloudstack.apache.org
Subject: Re: [VOTE] Release Apache CloudStack CloudMonkey 6.0.0

No sure if my vote counts, but a
[x] +1 approve
from me.

I built the tag 6.0.0 locally with Go 1.11.5 and tested against a CS
4.5.2 and a CS 4.11.2 instance.

Listing VMs and stopping/starting instances works as expected, on both 
CloudStack versions.

I also filed a few minor issues on Github, but nothing critical. The -p 
argument bug should be fixed in the next release if possible, though.

RE: New VP of CloudStack: Paul Angus

[Paul Angus]

Thank you everyone for your support, and again, HUGE thanks to Mike for his 
work last year!

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


-Original Message-
From: Wei ZHOU  
Sent: 11 March 2019 21:06
To: d...@cloudstack.apache.org
Subject: Re: New VP of CloudStack: Paul Angus

Congratulations Paul !
Thanks Mike for your amazing work  the past one year !

-Wei

Tutkowski, Mike  于2019年3月11日周一 下午4:16写道：

> Hi everyone,
>
> As you may know, the role of VP of CloudStack (Chair of the CloudStack
> PMC) has a one-year term. My term has now come and gone.
>
> I’m happy to announce that the CloudStack PMC has elected Paul Angus 
> as our new VP of CloudStack.
>
> As many already know, Paul has been an active member of the CloudStack 
> Community for over six years now. I’ve worked with Paul on and off 
> throughout much of that time and I believe he’ll be a great fit for 
> this role.
>
> Please join me in welcoming Paul as the new VP of Apache CloudStack!
>
> Thanks,
> Mike
>

RE: New* UI SVG hires icons for CloudStack (Vote)

[Paul Angus]

This is a great idea,  I wonder, could you refactor the code/positions on the 
sprite image to make dropping new icon sprites in generally easier?
Maybe have them in a rows, such that there is always a specific offset for 
'greyed out', 'selected', 'mouse over' etc ?
#scopecreep


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


-Original Message-
From: Sven Vogel  
Sent: 03 March 2019 12:57
To: users@cloudstack.apache.org; dev 
Subject: New* UI SVG hires icons for CloudStack (Vote)

Hi Cloudstack Users and Devs,

I create a new iconset for cloudstack and we think we will implement it. There 
is a Vote Formular and some examples. I oriented myself on the original one. 
Its a lot of work to make them all looks good but if you do not start it will 
be nothing. Lets start with the dashboard and left control panel.

https://form.jotformeu.com/90604064429354

Greetings from Leipzig



__

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.

RE: L2+ConfigDrive

[Paul Angus]

Hi Jean-Francois,

I suspect some extra work would need to be done in the managed storage plugin 
to create the iso on primary storage as storage 'locations' are only created on 
demand.


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


-Original Message-
From: Jean-Francois Nadeau  
Sent: 12 February 2019 12:45
To: users@cloudstack.apache.org
Cc: pi...@piszki.pl
Subject: Re: L2+ConfigDrive

Paul,  Is it true to say that parameter can only be enabled if you have NFS
primary storage enabled in the zone ?Or is there any chance this works
with managed storage ?

best,

Jfn

On Tue, Feb 12, 2019 at 4:29 AM Paul Angus  wrote:

> Great to hear that, thanks for letting us know!
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Piotr Pisz 
> Sent: 12 February 2019 06:54
> To: users@cloudstack.apache.org
> Subject: RE: L2+ConfigDrive
>
> Hi Angus,
>
> After changing the parameter vm.configdrive.primarypool.enabled to false
> everything works fine for the RBD pool.
> Thank you for your help :-)
>
> Regards,
> Piotr
>
>
> -Original Message-
> From: Paul Angus 
> Sent: Monday, February 11, 2019 7:31 PM
> To: users@cloudstack.apache.org; pi...@piszki.pl
> Subject: RE: L2+ConfigDrive
>
> In the global settings it is possible to specify whether you wish the
> config drive to be located on either primary or secondary storage. Perhaps
> you could check that the iso is being served from secondary storage, that
> was Ceph wouldn’t be involved.
> If it still doesn't work, please could you create a github issue for the
> problem.
>
> Kind regards
>
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Piotr Pisz 
> Sent: 11 February 2019 09:03
> To: users@cloudstack.apache.org
> Subject: RE: L2+ConfigDrive
>
> Hey Angus,
>
> My ACS is 4.11.2 with advanced network on KVM, config drive is enabled as
> network provider.
> I have done more tests, I have two ACS installations, one has Primary
> Storage as Ceph RBD and the other as SharedMountPoint.
> The error is for the RBD pool (see log), everything works fine for SMP.
>
> Piotr
>
>
> -Original Message-
> From: Paul Angus 
> Sent: Monday, February 11, 2019 9:25 AM
> To: users@cloudstack.apache.org; pi...@piszki.pl
> Subject: RE: L2+ConfigDrive
>
> Hi Piotr,
>
> Which version of CloudStack are you looking at?
> And, have you checked that configdrive is enabled as a network provider?
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Piotr Pisz 
> Sent: 10 February 2019 16:04
> To: users@cloudstack.apache.org
> Subject: L2+ConfigDrive
>
> Hello!
>
> I am interested in using Config Drive with the L2 network, unfortunately
> there is no word in the documentation for this topic.
> Has anyone used this and can guide me?
> Service offering L2 + ConfigDrive does not work, it is clearly missing (?)
> of the iso file.
> I have an error: Unable to start VM instance.
>
> Regards,
> Piotr
>
>
>

RE: UI Icons visibility when Started vs Stopped

[Paul Angus]

Thanks everyone,

Looks like there is a consensus that (as a general rule) we should try to 'grey 
out/disable' icons for features that the user can't access due to say whether a 
VM is started or stopped.  Icons for actions that can be used due to something 
like hypervisor type should probably just be hidden.

@devs - it would be great if everyone could try to follow this.  I hope that 
the ShapeBlue guys will be able to find time to migrate some icons to this 
style.  I'll try to get round to updating the sprite image in preparation to 
make it easier for folks.



From: Anurag Awasthi 
Sent: 20 February 2019 09:08
To: users@cloudstack.apache.org
Cc: Paul Angus 
Subject: Re: UI Icons visibility when Started vs Stopped

Hi all,

Since I have been only a few months into using CloudStack, from user's 
perspective, reading the correct doc and finding the right information is not 
always possible. There is definitely a need for a cleaner way to communicate 
available options about UI buttons.

However, I think there is no one solution fits all approach. In general greying 
out disabled buttons approach is more user friendly than completely hidden ui 
controls and misinformation. But it's not necessarily the best from positive 
experience note and can be discussed to vary on a case to case basis.
Regards,
Anurag Awasthi



Software Engineer
anurag.awas...@shapeblue.com<mailto:anurag.awas...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>








From: Rohit Yadav mailto:rohit.ya...@shapeblue.com>>
Sent: Wednesday, February 20, 2019 1:26 PM
To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
Cc: Paul Angus
Subject: Re: UI Icons visibility when Started vs Stopped

+1 to the specific question and also in general, all features (buttons/options) 
not available to users may be hidden or greyed out.


- Rohit

<https://cloudstack.apache.org>




From: Yordan Kostov 
mailto:yordan.kos...@worldsupport.info>>
Sent: Wednesday, February 20, 2019 1:09:11 PM
To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
Cc: Paul Angus
Subject: RE: UI Icons visibility when Started vs Stopped


+1 for greyed out.




rohit.ya...@shapeblue.com<mailto:rohit.ya...@shapeblue.com>
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue



From: calvin.l...@wingutechnology.com<mailto:calvin.l...@wingutechnology.com> 
[mailto:calvin.l...@wingutechnology.com]
Sent: Wednesday, February 20, 2019 1:42 AM
To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
Cc: Paul Angus mailto:paul.an...@shapeblue.com>>
Subject: Re: UI Icons visibility when Started vs Stopped



Paul:

As an end-user, I prefer to see the options greyed out.  The greyed out options 
serve as a teaching tool to expose all the potential benefits and features of a 
category.  In addition, it may be additionally helpful to link to a knowledge 
base with information regarding the greyed out function, it's benefits, and how 
to activate it.

With appreciation,
Calvin Levy, Technology Advisor



[Wingu Technology - The New Standard In Business Information Technology]

Wingu Technology LLC | 2252 Twelve Oaks Way, Suite 102 | Wesley Chapel, Florida 
33544-6972

+1 (813) 397-8400 ext. 2000 | 
calvin.l...@wingutechnology.com<mailto:calvin.l...@wingutechnology.com<mailto:calvin.l...@wingutechnology.com%3cmailto:calvin.l...@wingutechnology.com>>
 | https://wingutechnology.com

BIG Technology for Small Businesses
The New Standard In Business Information Technology.

[Wingu Technology 
LinkedIn]<https://www.linkedin.com/in/calvin-levy-a590a3126/>[Wingu Technology 
Facebook]<https://www.facebook.com/WinguTechnology>[Wingu Technology 
Instagram]<https://www.instagram.com/wingutechnology/>[Wingu Technology 
Twitter]<https://twitter.com/WinguTechnology>[Wingu Technology 
Website]<https://wingutechnology.com>[Wingu Technology 
Blog]<https://wingutechnology.com/index.php/team/blog>[Wingu Technology 
YouTube]<https://www.youtube.com/channel/UCJpzDhgWBwnaVh4ut7NP7mw>

Cyber-Security | Private Cloud Solutions | Business Continuity | Disaster 
Recovery | Compliance
VOIP Phone Systems | Business Applications | Monitoring & Support | Hardened & 
Secure Systems

(WINGU pronounced "wee-in-goo" is Swahili for Cloud)

Email Disclaimer: The information contained in this transmission may contain 
privileged and confidential information, including customer information 
protected by federal and state privacy laws. It is intended only for the use of 
the person(s) named above. If you are not the intended recipient, you are 
hereby notified that any review, dissemination, distribution, or duplication of 
this communication is strictly prohibited. If you are not the intended 
recipient, please contac

RE: installation troubles

[Paul Angus]

Hi Gregor,

If you can, would you mind submitting a pull request to the documentation repo 
https://github.com/apache/cloudstack-documentation
to add the missing steps?

Many thanks
Paul Angus

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


-Original Message-
From: Riepl, Gregor (SWISS TXT)  
Sent: 26 February 2019 09:59
To: users@cloudstack.apache.org
Subject: Re: installation troubles

Hi,

> I'm not sure the community is able to help you with local DEB repo you 
> host in the network. Try to use the guide and install from the 
> official repository.

I think Alejandro *was* following the guide. It specifically explains how to 
build your own CloudStack packages and set up a dpkg repository:
http://docs.cloudstack.apache.org/en/4.11.2.0/installguide/building_fro
m_source.html#building-deb-packages


Those instructions are incomplete.
To create a valid Debian repo, you also need a Release file, and you should 
probably keep the uncompressed Packages file as well.

I use the following script to do this:

dpkg-scanpackages . /dev/null > Packages gzip -9k Packages apt-ftparchive 
release . > Release

To generate signatures, use:

gpg --clearsign --digest-algo SHA512 -o InRelease Release gpg -abs 
--digest-algo SHA512 -o Release.gpg Release


Regards,
Gregor