FW: Google Summer of Code 2017 is coming

[Giles Sirett]

All
See below - Google Summer of code 2017 isn't far away.
Previously, we've had a number of project committers who have come to us 
through a GSOC project

Become a mentor isn't something to be taken lightly but I would encourage as 
many of our community as possible to consider it - it will hopefully help wth 
the next generation of people excited to work on cloudstack




Kind Regards
Giles


giles.sir...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Ulrich Stärk [mailto:u...@apache.org] 
Sent: 03 February 2017 19:51
To: ment...@community.apache.org
Subject: Google Summer of Code 2017 is coming

Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing students to 
spend their summer working on open source software. Students will receive 
stipends for developing open source software full-time for three months. 
Projects will provide mentoring and project ideas, and in return have the 
chance to get new code developed and - most importantly - to identify and bring 
in new committers.

The ASF will apply as a participating organization meaning individual projects 
don't have to apply separately.

If you want to participate with your project we ask you to do the following 
things as soon as possible but by no later than 2017-02-09:

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2017, and they will show up at 
[3]. Please be as specific as possible when describing your idea. Include the 
programming language, the tools and skills required, but try not to scare 
potential students away. They are supposed to learn what's required before the 
program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang, python, 
brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...) and record 
them at [5].

Please use the COMDEV JIRA project for recording your ideas if your project 
doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2017 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential mentors, 
meant to be used as a private list - general discussions on the public 
d...@community.apache.org list as much as possible please). Use a recognized 
address when subscribing (@apache.org or one of your alias addresses on record).

Note that the ASF isn't accepted as a participating organization yet, 
nevertheless you *have to* start recording your ideas now or we will not get 
accepted.

Over the years we were able to complete hundreds of projects successfully. Some 
of our prior students are active contributors now! Let's make this year a 
success again!

Cheers,

Uli

P.S.: Except for the private parts (label spreadsheet mostly), this email is 
free to be shared publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] http://s.apache.org/gsoc2017ideas
[4] http://community.apache.org/gsoc.html
[5] http://s.apache.org/gsoclabels

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: Optimize vm expunge process for ins...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
Hi @nvazquez 
Did the behavior in step2 change with this PR or is it same as earlier?
Can you please add the testing already done?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: FW: Google Summer of Code 2017 is coming

[Wido den Hollander]

> Op 6 februari 2017 om 9:51 schreef Giles Sirett :
> 
> 
> All
> See below - Google Summer of code 2017 isn't far away.
> Previously, we've had a number of project committers who have come to us 
> through a GSOC project
> 

Do we have small sized projects / ideas ready to be submitted for GSOC?

> Become a mentor isn't something to be taken lightly but I would encourage as 
> many of our community as possible to consider it - it will hopefully help wth 
> the next generation of people excited to work on cloudstack

Did this for the Ceph project. It is a lot of work.

Wido

> 
> 
> 
> 
> Kind Regards
> Giles
> 
> 
> giles.sir...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> 
> -Original Message-
> From: Ulrich Stärk [mailto:u...@apache.org] 
> Sent: 03 February 2017 19:51
> To: ment...@community.apache.org
> Subject: Google Summer of Code 2017 is coming
> 
> Hello PMCs (incubator Mentors, please forward this email to your podlings),
> 
> Google Summer of Code [1] is a program sponsored by Google allowing students 
> to spend their summer working on open source software. Students will receive 
> stipends for developing open source software full-time for three months. 
> Projects will provide mentoring and project ideas, and in return have the 
> chance to get new code developed and - most importantly - to identify and 
> bring in new committers.
> 
> The ASF will apply as a participating organization meaning individual 
> projects don't have to apply separately.
> 
> If you want to participate with your project we ask you to do the following 
> things as soon as possible but by no later than 2017-02-09:
> 
> 1. understand what it means to be a mentor [2].
> 
> 2. record your project ideas.
> 
> Just create issues in JIRA, label them with gsoc2017, and they will show up 
> at [3]. Please be as specific as possible when describing your idea. Include 
> the programming language, the tools and skills required, but try not to scare 
> potential students away. They are supposed to learn what's required before 
> the program starts.
> 
> Use labels, e.g. for the programming language (java, c, c++, erlang, python, 
> brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...) and 
> record them at [5].
> 
> Please use the COMDEV JIRA project for recording your ideas if your project 
> doesn't use JIRA (e.g.
> httpd, ooo). Contact d...@community.apache.org if you need assistance.
> 
> [4] contains some additional information (will be updated for 2017 shortly).
> 
> 3. subscribe to ment...@community.apache.org; restricted to potential 
> mentors, meant to be used as a private list - general discussions on the 
> public d...@community.apache.org list as much as possible please). Use a 
> recognized address when subscribing (@apache.org or one of your alias 
> addresses on record).
> 
> Note that the ASF isn't accepted as a participating organization yet, 
> nevertheless you *have to* start recording your ideas now or we will not get 
> accepted.
> 
> Over the years we were able to complete hundreds of projects successfully. 
> Some of our prior students are active contributors now! Let's make this year 
> a success again!
> 
> Cheers,
> 
> Uli
> 
> P.S.: Except for the private parts (label spreadsheet mostly), this email is 
> free to be shared publicly if you want to.
> 
> [1] https://summerofcode.withgoogle.com/
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2017ideas
> [4] http://community.apache.org/gsoc.html
> [5] http://s.apache.org/gsoclabels
> 
>

Re: FW: Google Summer of Code 2017 is coming

[Daan Hoogland]

I'll do some jira grooming the next couple of days, maybe we find some.


From: Wido den Hollander 
Sent: 06 February 2017 10:59:07
To: Giles Sirett; dev@cloudstack.apache.org
Subject: Re: FW: Google Summer of Code 2017 is coming


> Op 6 februari 2017 om 9:51 schreef Giles Sirett :
>
>
> All
> See below - Google Summer of code 2017 isn't far away.
> Previously, we've had a number of project committers who have come to us 
> through a GSOC project
>

Do we have small sized projects / ideas ready to be submitted for GSOC?

> Become a mentor isn't something to be taken lightly but I would encourage as 
> many of our community as possible to consider it - it will hopefully help wth 
> the next generation of people excited to work on cloudstack

Did this for the Ceph project. It is a lot of work.

Wido

>
>
>
>
> Kind Regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Ulrich Stärk [mailto:u...@apache.org]
> Sent: 03 February 2017 19:51
> To: ment...@community.apache.org
> Subject: Google Summer of Code 2017 is coming
>
> Hello PMCs (incubator Mentors, please forward this email to your podlings),
>
> Google Summer of Code [1] is a program sponsored by Google allowing students 
> to spend their summer working on open source software. Students will receive 
> stipends for developing open source software full-time for three months. 
> Projects will provide mentoring and project ideas, and in return have the 
> chance to get new code developed and - most importantly - to identify and 
> bring in new committers.
>
> The ASF will apply as a participating organization meaning individual 
> projects don't have to apply separately.
>
> If you want to participate with your project we ask you to do the following 
> things as soon as possible but by no later than 2017-02-09:
>
> 1. understand what it means to be a mentor [2].
>
> 2. record your project ideas.
>
> Just create issues in JIRA, label them with gsoc2017, and they will show up 
> at [3]. Please be as specific as possible when describing your idea. Include 
> the programming language, the tools and skills required, but try not to scare 
> potential students away. They are supposed to learn what's required before 
> the program starts.
>
> Use labels, e.g. for the programming language (java, c, c++, erlang, python, 
> brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...) and 
> record them at [5].
>
> Please use the COMDEV JIRA project for recording your ideas if your project 
> doesn't use JIRA (e.g.
> httpd, ooo). Contact d...@community.apache.org if you need assistance.
>
> [4] contains some additional information (will be updated for 2017 shortly).
>
> 3. subscribe to ment...@community.apache.org; restricted to potential 
> mentors, meant to be used as a private list - general discussions on the 
> public d...@community.apache.org list as much as possible please). Use a 
> recognized address when subscribing (@apache.org or one of your alias 
> addresses on record).
>
> Note that the ASF isn't accepted as a participating organization yet, 
> nevertheless you *have to* start recording your ideas now or we will not get 
> accepted.
>
> Over the years we were able to complete hundreds of projects successfully. 
> Some of our prior students are active contributors now! Let's make this year 
> a success again!
>
> Cheers,
>
> Uli
>
> P.S.: Except for the private parts (label spreadsheet mostly), this email is 
> free to be shared publicly if you want to.
>
> [1] https://summerofcode.withgoogle.com/
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2017ideas
> [4] http://community.apache.org/gsoc.html
> [5] http://s.apache.org/gsoclabels
>
>

daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
@shapeblue
  
 

Re: FW: Google Summer of Code 2017 is coming

[Daan Hoogland]

I think we should be able to muster some quickly:

project = CLOUDSTACK AND issuetype in (Improvement, "New Feature", Wish) AND 
status = Open AND assignee in (EMPTY)

leads me to 321 open, unassigned, wishes, improvements and new features [😉]


I'll do some filtering and maybe we can group ideas in this thread quickly



daan.hoogl...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, Utrecht Utrecht 3531 VENetherlands
@shapeblue
  
 

From: Daan Hoogland
Sent: 06 February 2017 11:02:29
To: Giles Sirett; dev@cloudstack.apache.org
Subject: Re: FW: Google Summer of Code 2017 is coming


I'll do some jira grooming the next couple of days, maybe we find some.


From: Wido den Hollander 
Sent: 06 February 2017 10:59:07
To: Giles Sirett; dev@cloudstack.apache.org
Subject: Re: FW: Google Summer of Code 2017 is coming


> Op 6 februari 2017 om 9:51 schreef Giles Sirett :
>
>
> All
> See below - Google Summer of code 2017 isn't far away.
> Previously, we've had a number of project committers who have come to us 
> through a GSOC project
>

Do we have small sized projects / ideas ready to be submitted for GSOC?

> Become a mentor isn't something to be taken lightly but I would encourage as 
> many of our community as possible to consider it - it will hopefully help wth 
> the next generation of people excited to work on cloudstack

Did this for the Ceph project. It is a lot of work.

Wido

>
>
>
>
> Kind Regards
> Giles
>
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Ulrich Stärk [mailto:u...@apache.org]
> Sent: 03 February 2017 19:51
> To: ment...@community.apache.org
> Subject: Google Summer of Code 2017 is coming
>
> Hello PMCs (incubator Mentors, please forward this email to your podlings),
>
> Google Summer of Code [1] is a program sponsored by Google allowing students 
> to spend their summer working on open source software. Students will receive 
> stipends for developing open source software full-time for three months. 
> Projects will provide mentoring and project ideas, and in return have the 
> chance to get new code developed and - most importantly - to identify and 
> bring in new committers.
>
> The ASF will apply as a participating organization meaning individual 
> projects don't have to apply separately.
>
> If you want to participate with your project we ask you to do the following 
> things as soon as possible but by no later than 2017-02-09:
>
> 1. understand what it means to be a mentor [2].
>
> 2. record your project ideas.
>
> Just create issues in JIRA, label them with gsoc2017, and they will show up 
> at [3]. Please be as specific as possible when describing your idea. Include 
> the programming language, the tools and skills required, but try not to scare 
> potential students away. They are supposed to learn what's required before 
> the program starts.
>
> Use labels, e.g. for the programming language (java, c, c++, erlang, python, 
> brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...) and 
> record them at [5].
>
> Please use the COMDEV JIRA project for recording your ideas if your project 
> doesn't use JIRA (e.g.
> httpd, ooo). Contact d...@community.apache.org if you need assistance.
>
> [4] contains some additional information (will be updated for 2017 shortly).
>
> 3. subscribe to ment...@community.apache.org; restricted to potential 
> mentors, meant to be used as a private list - general discussions on the 
> public d...@community.apache.org list as much as possible please). Use a 
> recognized address when subscribing (@apache.org or one of your alias 
> addresses on record).
>
> Note that the ASF isn't accepted as a participating organization yet, 
> nevertheless you *have to* start recording your ideas now or we will not get 
> accepted.
>
> Over the years we were able to complete hundreds of projects successfully. 
> Some of our prior students are active contributors now! Let's make this year 
> a success again!
>
> Cheers,
>
> Uli
>
> P.S.: Except for the private parts (label spreadsheet mostly), this email is 
> free to be shared publicly if you want to.
>
> [1] https://summerofcode.withgoogle.com/
> [2] http://community.apache.org/guide-to-being-a-mentor.html
> [3] http://s.apache.org/gsoc2017ideas
> [4] http://community.apache.org/gsoc.html
> [5] http://s.apache.org/gsoclabels
>
>

[GitHub] cloudstack pull request #1934: [CLOUDSTACK-9772] Template: perform a HEAD re...

[marcaurele]

GitHub user marcaurele opened a pull request:

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

[CLOUDSTACK-9772] Template: perform a HEAD request to check file size from 
a URL

Signed-off-by: Marc-Aurèle Brothier 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/exoscale/cloudstack fix/CLOUDSTACK-9772

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1934.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1934


commit 46fb454f4deb6c36f52a6e943b1f23c45508ab04
Author: Marc-Aurèle Brothier 
Date:   2017-02-06T12:51:14Z

Template: perform a HEAD request to check file size from a URL

Signed-off-by: Marc-Aurèle Brothier 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: FW: Google Summer of Code 2017 is coming

[Ian Duffy]

I believe Sachin (CCed) was showed interest in becoming a student a couple
of months back. Might be good to get him and a potential mentor talking.

On 6 February 2017 at 10:19, Daan Hoogland 
wrote:

> I think we should be able to muster some quickly:
>
> project = CLOUDSTACK AND issuetype in (Improvement, "New Feature", Wish)
> AND status = Open AND assignee in (EMPTY)
>
> leads me to 321 open, unassigned, wishes, improvements and new features 
> [image:
> 😉]
>
>
> I'll do some filtering and maybe we can group ideas in this thread quickly
>
> daan.hoogl...@shapeblue.com
> www.shapeblue.com
> @shapeblue
>
>
>
> --
> *From:* Daan Hoogland
> *Sent:* 06 February 2017 11:02:29
> *To:* Giles Sirett; dev@cloudstack.apache.org
> *Subject:* Re: FW: Google Summer of Code 2017 is coming
>
>
> I'll do some jira grooming the next couple of days, maybe we find some.
> --
> *From:* Wido den Hollander 
> *Sent:* 06 February 2017 10:59:07
> *To:* Giles Sirett; dev@cloudstack.apache.org
> *Subject:* Re: FW: Google Summer of Code 2017 is coming
>
>
> > Op 6 februari 2017 om 9:51 schreef Giles Sirett <
> giles.sir...@shapeblue.com>:
> >
> >
> > All
> > See below - Google Summer of code 2017 isn't far away.
> > Previously, we've had a number of project committers who have come to us
> through a GSOC project
> >
>
> Do we have small sized projects / ideas ready to be submitted for GSOC?
>
> > Become a mentor isn't something to be taken lightly but I would
> encourage as many of our community as possible to consider it - it will
> hopefully help wth the next generation of people excited to work on
> cloudstack
>
> Did this for the Ceph project. It is a lot of work.
>
> Wido
>
> >
> >
> >
> >
> > Kind Regards
> > Giles
> >
> >
> > giles.sir...@shapeblue.com
> > www.shapeblue.com
> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > @shapeblue
> >
> >
> >
> >
> > -Original Message-
> > From: Ulrich Stärk [mailto:u...@apache.org ]
> > Sent: 03 February 2017 19:51
> > To: ment...@community.apache.org
> > Subject: Google Summer of Code 2017 is coming
> >
> > Hello PMCs (incubator Mentors, please forward this email to your
> podlings),
> >
> > Google Summer of Code [1] is a program sponsored by Google allowing
> students to spend their summer working on open source software. Students
> will receive stipends for developing open source software full-time for
> three months. Projects will provide mentoring and project ideas, and in
> return have the chance to get new code developed and - most importantly -
> to identify and bring in new committers.
> >
> > The ASF will apply as a participating organization meaning individual
> projects don't have to apply separately.
> >
> > If you want to participate with your project we ask you to do the
> following things as soon as possible but by no later than 2017-02-09:
> >
> > 1. understand what it means to be a mentor [2].
> >
> > 2. record your project ideas.
> >
> > Just create issues in JIRA, label them with gsoc2017, and they will show
> up at [3]. Please be as specific as possible when describing your idea.
> Include the programming language, the tools and skills required, but try
> not to scare potential students away. They are supposed to learn what's
> required before the program starts.
> >
> > Use labels, e.g. for the programming language (java, c, c++, erlang,
> python, brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...)
> and record them at [5].
> >
> > Please use the COMDEV JIRA project for recording your ideas if your
> project doesn't use JIRA (e.g.
> > httpd, ooo). Contact d...@community.apache.org if you need assistance.
> >
> > [4] contains some additional information (will be updated for 2017
> shortly).
> >
> > 3. subscribe to ment...@community.apache.org; restricted to potential
> mentors, meant to be used as a private list - general discussions on the
> public d...@community.apache.org list as much as possible please). Use a
> recognized address when subscribing (@apache.org or one of your alias
> addresses on record).
> >
> > Note that the ASF isn't accepted as a participating organization yet,
> nevertheless you *have to* start recording your ideas now or we will not
> get accepted.
> >
> > Over the years we were able to complete hundreds of projects
> successfully. Some of our prior students are active contributors now! Let's
> make this year a success again!
> >
> > Cheers,
> >
> > Uli
> >
> > P.S.: Except for the private parts (label spreadsheet mostly), this
> email is free to be shared publicly if you want to.
> >
> > [1] https://summerofcode.withgoogle.com/
> > [2] http://community.apache.org/guide-to-being-a-mentor.html
> > [3] http://s.apache.org/gsoc2017ideas
> > [4] http://community.apache.org/gsoc.html
> > [5] http://s.apache.org/gsoclabels
> >
> >
>

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[borisstoyanov]

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

[borisstoyanov]

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
@swill blueorangutan package builds a yum repo from the PR, but it doesn't 
build new system vms, we'll need to build them manually, build an env with the 
packages, update the ssvm and kick the tests manually AFAIK. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-473


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

[swill]

Github user swill commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
@borisstoyanov thanks.  Yes, that explains why there are failures.  When I 
ran my tests, I did it with a system VM built from this PR: 
https://github.com/apache/cloudstack/pull/1741#issuecomment-273827361

Is it possible to manually build the system VM template and specify it when 
testing with Trillian.  I can see if I can build and expose publicly templates 
for Xen and KVM if that helps.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1935: CLOUDSTACK-9764: Delete domain failure due to...

[nvazquez]

GitHub user nvazquez opened a pull request:

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

CLOUDSTACK-9764: Delete domain failure due to Account Cleanup task

It was noticed in production environments that `deleteDomain` task failed 
for domains with multiple accounts and resources. Examining logs it was found 
out that if Account Cleanup Task got executed after domain (and all of its 
subchilds) got marked as Inactive; and before delete domain task finishes, it 
produces a failure.

`AccountCleanupTask` gets executed every `account.cleanup.interval` seconds 
looking for:
* Removed accounts
* Disabled accounts
* Inactive domains

As `deleteDomain` marks domain to delete (and its subchilds) as Inactive 
before deleting them, when `AccountCleanupTask` is executed, it removes marked 
domains. When there are resources to cleanup on domain accounts, domain is not 
found throwing exception: `com.cloud.exception.InvalidParameterValueException: 
Please specify a valid domain ID`

### Example
`account.cleanup.interval` = 100


2017-01-26 06:07:03,621 DEBUG [cloud.api.ApiServlet] 
(catalina-exec-8:ctx-50cfa3b6 ctx-92ad5b38) ===END===  10.39.251.17 -- GET  
command=deleteDomain&id=1910a3dc-6fa6-457b-ab3a-602b0cfb6686&cleanup=true&response=json&_=1485439623475

...

// Domain and its subchilds marked as Inactive
2017-01-26 06:07:03,640 DEBUG [cloud.user.DomainManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Marking domain id=27 
as Inactive before actually deleting it
2017-01-26 06:07:03,646 DEBUG [cloud.user.DomainManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Cleaning up domain 
id=27
2017-01-26 06:07:03,670 DEBUG [cloud.user.DomainManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Cleaning up domain 
id=28
2017-01-26 06:07:03,685 DEBUG [cloud.user.DomainManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Cleaning up domain 
id=29

...

// AccountCleanupTask removes Inactive domain id=29, no rollback for it
2017-01-26 06:07:44,285 INFO  [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Found 0 removed accounts to cleanup
2017-01-26 06:07:44,287 INFO  [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Found 0 disabled accounts to cleanup
2017-01-26 06:07:44,289 INFO  [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Found 3 inactive domains to cleanup
2017-01-26 06:07:44,292 DEBUG [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Removing inactive domain id=27
2017-01-26 06:07:44,297 DEBUG [db.Transaction.Transaction] 
(AccountChecker-1:ctx-b8a01824) Rolling back the transaction: Time = 2 Name =  
AccountChecker-1; called by 
-TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:204-$Proxy63.remove:-1-DomainManagerImpl.removeDomain:248-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62
2017-01-26 06:07:44,301 DEBUG [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Removing inactive domain id=28
2017-01-26 06:07:44,304 DEBUG [db.Transaction.Transaction] 
(AccountChecker-1:ctx-b8a01824) Rolling back the transaction: Time = 2 Name =  
AccountChecker-1; called by 
-TransactionLegacy.rollback:889-TransactionLegacy.removeUpTo:832-TransactionLegacy.close:656-TransactionContextInterceptor.invoke:36-ReflectiveMethodInvocation.proceed:161-ExposeInvocationInterceptor.invoke:91-ReflectiveMethodInvocation.proceed:172-JdkDynamicAopProxy.invoke:204-$Proxy63.remove:-1-DomainManagerImpl.removeDomain:248-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62
2017-01-26 06:07:44,307 DEBUG [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Removing inactive domain id=29
2017-01-26 06:07:44,319 INFO  [cloud.user.AccountManagerImpl] 
(AccountChecker-1:ctx-b8a01824) Found 0 disabled projects to cleanup

...

// Failure due to domain is already removed
2017-01-26 06:07:46,369 WARN  [cloud.user.AccountManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Failed to cleanup 
account Acct[6a6e63ad-d89b-4a53-b3ae-1c06ea3d1899-ac2] due to 
com.cloud.exception.InvalidParameterValueException: Please specify a valid 
domain ID.
at 
com.cloud.resourcelimit.ResourceLimitManagerImpl.recalculateResourceCount(ResourceLimitManagerImpl.java:752)
at com.cloud.vm.UserVmManagerImpl.expunge(UserVmManagerImpl.java:2053)
...
2017-01-26 06:07:46,381 INFO  [cloud.user.AccountManagerImpl] 
(API-Job-Executor-29:ctx-23415942 job-7165 ctx-fe3d13d6) Cleanup for account 
2580 is needed.
2017-01-26 06:07:46,390 DEBUG [cloud.us

Re: Slack archive

[Will Stevens]

I think doing the Free version would make sense.  +1

*Will STEVENS*
Lead Developer



On Fri, Feb 3, 2017 at 2:56 AM, Erik Weber  wrote:

> Hi all,
>
> I recently wanted to link some content from our Slack channel but
> couldn't find a way, would it make sense to use something like
> http://slackarchive.io/?
>
> I do know that mail is the only accepted communication for decisions
> etc, but having our slack history publicly available makes it easier
> to refer to and for others to find.
>
> --
> Erik
>

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[borisstoyanov]

Github user borisstoyanov commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
@blueorangutan test 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has 
been kicked to run smoke tests


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [PROPOSAL] add native container orchestration service

[Syed Ahmed]

Sorry for jumping into this late. I was swamped with work and finally found
some time to look at this. I like the idea of havig a native container
cluster. I think this can be very powerful to natively provision any of the
container orchestrators. I also think that orchestrating containers should
not be done by Cloudstack but should be offloaded to other orchestrators
while Cloudstack provides the low level provisioning of VMs and networks.
This could also be very powerful with baremetal provisioning(something
which I've been working on recently). Cloudstack can provision baremetal
servers which can run k8s or Mesos. This would give a lot of power and
flexibility to users who want performance.

Here are my comments:

1. Is the assumption that the container orchestrator (k8s or Mesos) are
already installed and running elsewhere? or does Cloudstack spin up a VM
and install them. Depending on what happens, there will be different
questions. For example, if CS is installing k8s, how would it do it? or if
k8s is already installed, how would the network rules configured so that it
can reach the VMs

2. What are `memory` and `cores` in the `container_cluster` table used for
given you already have service offering and number of nodes.

3. When in `Alert` state, if the recovery fails, does it give up or keeps
trying? Also, is the switching between `Alert` and `Recover` state timeout
based?


Other than the above comments it looks good from my side. Kudos Murali!

On Fri, Feb 3, 2017 at 9:20 AM, Kishan Kavala 
wrote:

> Murali,
>  APIs are similar, but the name is generic - createServiceCluster instead
> of createContainerCluster
> Same with DB tables names - service_cluster instead of container_cluster
> API params or the DB columns in the spec you published don't have anything
> specific to container_clusters and can be used for any service.
>
> -Original Message-
> From: Murali Reddy [mailto:muralimmre...@gmail.com]
> Sent: 02 February 2017 02:34 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
>
> Thanks for the feedback. There have been some concerns here with this
> proposal. I think we had sufficient valid arguments why we need this
> functionality in CloudStack. While this proposal is to use k8s as container
> orchestrator design should be able to adopt other container orchestrator.
>
>
> Unless anybody has any specific technical points on this, I'd like to go
> on with its implementation and open up a PR.
>
>
> Kishan, when do you think you can share further details (northbound API
> semantics etc) on the work you are doing? I am planning to get this feature
> the for 4.11.
>
>
>
> On 31/01/17, 5:54 PM, "Will Stevens"  wrote:
>
> >I think that is covered in this proposal. There is nothing k8s specific
> >in this integration (from what I understand), all the k8s details are
> >passed in via the cloud-init configuration after the cluster has been
> provisioned.
> >
> >On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> wrote:
> >
> >
> >There are many container orchestrators. Those container orchestrators
> >are happy to run on any VMs or bare metal machines. K8s is just one of
> >them and there will be more in the future. It may not be a good idea to
> >make CloudStack to be k8s aware. IMO, the relationship between k8s and
> >cloudstack should be similar to application and os. It probably not a
> >good idea to make your OS to be aware of any specific applications so
> >IMHO I don’t think k8s should be native to CloudStack. It makes more
> >sense to provide some generic services that many applications can take
> >advantages of. Some generic resource grouping service makes sense so a
> >group of VMs, baremetal machines or network can be treated as a single
> >entity. Some life cycle management will be necessary for these entities
> >too. We can deploy k8s, swarm, dcos or even non-container specific
> >services on top of CloudStack. The k8s is changing fast. One single
> >tenant installation may need more than one VM group and may actually
> >requires more (k8s federation). It will be a struggle to be in sync if
> >we try to bring k8s specific knowledge into cloudstack.
> >
> >Regards,
> >
> >
> >--
> >Lianghwa Jou
> >VP Engineering, Accelerite
> >email: lianghwa@accelerite.com
> >
> >
> >
> >
> >
> >On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
> >
> >
> >I agree with some good views Will has shared and I also agree to
> >the concerns raised by Wido and Eric. IMO we need balance of staying
> >relevant/add new features vs stability of CloudStack and take
> >corrective action if needed. We have two good examples for both. When
> >SDN was hot technology CloudStack ended up with bunch of SDN controller
> integrations.
> >Few years later, now CloudStack is carrying baggage with no maintainers
> >for those plugins, with probably not many of CloudStack users needing
> overlays.
> >On the other hand, other than attempt to liaison with ETSI for NFV no
> >ef

Re: Slack archive

[Simon Weller]

Yes, I agree. Some of us use slack quite a lot. I have a slack to IRC bridge 
setup as well, so any slack discussion in the general channel gets replicated 
over to cloudstack IRC and vice versa.


- Si



From: williamstev...@gmail.com  on behalf of Will 
Stevens 
Sent: Monday, February 6, 2017 9:54 AM
To: dev@cloudstack.apache.org
Subject: Re: Slack archive

I think doing the Free version would make sense.  +1

*Will STEVENS*
Lead Developer


CloudOps | Managed Private Cloud | Managed Public Cloud | Cloud Building | 
Cloud Architecture | Cloud Migration
goo.gl
We provide private, public and hybrid cloud solutions for businesses seeking to 
scale, and for enterprises making their move to the Cloud.




On Fri, Feb 3, 2017 at 2:56 AM, Erik Weber  wrote:

> Hi all,
>
> I recently wanted to link some content from our Slack channel but
> couldn't find a way, would it make sense to use something like
> http://slackarchive.io/?
SlackArchive.io - Public chat archive for your Slack 
team
slackarchive.io
Public archive. Give your community access to full slack chat history to find 
the solutions that were already answered.



>
> I do know that mail is the only accepted communication for decisions
> etc, but having our slack history publicly available makes it easier
> to refer to and for others to find.
>
> --
> Erik
>

RE: [PROPOSAL] add native container orchestration service

[Paul Angus]

#WhatHeSaid

The title is misleading.  The proposal is purely to add the notion of Clusters 
of VMs to CloudStack.  These may be for databases, containers or anything else 
that needs 'clusters' of compute. Self-healing and autoscaling are logical next 
steps to be added. 

Those guys at ShapeBlue have open-sourced their whole k8s container service 
piece.  If/when the 'cluster' part of that work is added into CloudStack, the 
k8s specific pieces can be used by anyone who wants to, alternatively they 
could be used for reference in order to create another types of cluster.  (or 
ignored completely).




paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com] 
Sent: 31 January 2017 13:26
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

s/cloud-init/cloud-config/

On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:

> I think that is covered in this proposal. There is nothing k8s 
> specific in this integration (from what I understand), all the k8s 
> details are passed in via the cloud-init configuration after the cluster has 
> been provisioned.
>
> On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> wrote:
>
>
> There are many container orchestrators. Those container orchestrators 
> are happy to run on any VMs or bare metal machines. K8s is just one of 
> them and there will be more in the future. It may not be a good idea 
> to make CloudStack to be k8s aware. IMO, the relationship between k8s 
> and cloudstack should be similar to application and os. It probably 
> not a good idea to make your OS to be aware of any specific 
> applications so IMHO I don’t think k8s should be native to CloudStack. 
> It makes more sense to provide some generic services that many 
> applications can take advantages of. Some generic resource grouping 
> service makes sense so a group of VMs, baremetal machines or network 
> can be treated as a single entity. Some life cycle management will be 
> necessary for these entities too. We can deploy k8s, swarm, dcos or 
> even non-container specific services on top of CloudStack. The k8s is 
> changing fast. One single tenant installation may need more than one 
> VM group and may actually requires more (k8s federation). It will be a 
> struggle to be in sync if we try to bring k8s specific knowledge into 
> cloudstack.
>
> Regards,
>
>
> --
> Lianghwa Jou
> VP Engineering, Accelerite
> email: lianghwa@accelerite.com
>
>
>
>
>
> On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
>
>
> I agree with some good views Will has shared and I also agree to 
> the concerns raised by Wido and Eric. IMO we need balance of staying 
> relevant/add new features vs stability of CloudStack and take 
> corrective action if needed. We have two good examples for both. When 
> SDN was hot technology CloudStack ended up with bunch of SDN controller 
> integrations.
> Few years later, now CloudStack is carrying baggage with no 
> maintainers for those plugins, with probably not many of CloudStack users 
> needing overlays.
> On the other hand, other than attempt to liaison with ETSI for NFV no 
> effort was done. OpenStack has become de-facto for NFV. Now for 
> OpenStack, arguably NFV has become larger use case than cloud it self. 
> I concur with Will’s point that with minimal viable solution that does 
> not change the core of CloudStack, and can keep CloudStack relevant is 
> worth to be taken in.
>
> Will,
>
> To your question of how different is from ShapeBlue’s container 
> service, its design, implementation and API semantics etc remain same.
> ShapeBlue’s container service was true drop in plug-in to CloudStack, 
> with this proposal I am trying to re-work to make it a core CloudStack 
> pluggable service which is part of CloudStack.
>
> Key concepts that this proposal is trying to add
>
> - add notion of ‘container cluster’ as a first class entity in 
> CloudStack. Which is bacially collection of other CloudStack resources 
> (like VM’s, networks, public ip, network rules etc)
> - life cycle operation to manage ‘container cluster’ like 
> create, delete, start, stop, scale-up, scale-down, heal etc
> - orchestrate container orchestrator control plane on top of 
> provisioned resources
>
> At-least for k8s (which is what this proposal is targeting), 
> integration with k8s is bare minimum. There are cloud-config scripts 
> that automatically setup k8s cluster master and node VM’s. All 
> CloudStack is doing in passing the cloud-config to the core OS VM’s as user 
> data.
>
> Regards
> Murali Reddy
>
>
>
>
>
>
>
> On 29/01/17, 8:54 AM, "Will Stevens"  behalf of wstev...@cloudops.com> wrote:
>
> >I agree that we need to be careful what we take on and own inside
> >CloudStack.  I feel like some of the plugins or integrations 
> which we have
> >been "maintaini

RE: [PROPOSAL] add native container orchestration service

[Rajesh Ramchandani]

Hi Paul - I think this is different from what the thread was about. The 
conversation was specifically about adding support for container orchestrators. 
You are talking about provisioning a group of VMs. Although, this is something 
I think several Cloudstack users have requested before and we should propose a 
solution to this.

Raj


From: Paul Angus 
Sent: Monday, February 6, 2017 11:16:41 AM
To: dev@cloudstack.apache.org
Subject: RE: [PROPOSAL] add native container orchestration service

#WhatHeSaid

The title is misleading.  The proposal is purely to add the notion of Clusters 
of VMs to CloudStack.  These may be for databases, containers or anything else 
that needs 'clusters' of compute. Self-healing and autoscaling are logical next 
steps to be added.

Those guys at ShapeBlue have open-sourced their whole k8s container service 
piece.  If/when the 'cluster' part of that work is added into CloudStack, the 
k8s specific pieces can be used by anyone who wants to, alternatively they 
could be used for reference in order to create another types of cluster.  (or 
ignored completely).




paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue




-Original Message-
From: Will Stevens [mailto:williamstev...@gmail.com]
Sent: 31 January 2017 13:26
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

s/cloud-init/cloud-config/

On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:

> I think that is covered in this proposal. There is nothing k8s
> specific in this integration (from what I understand), all the k8s
> details are passed in via the cloud-init configuration after the cluster has 
> been provisioned.
>
> On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> wrote:
>
>
> There are many container orchestrators. Those container orchestrators
> are happy to run on any VMs or bare metal machines. K8s is just one of
> them and there will be more in the future. It may not be a good idea
> to make CloudStack to be k8s aware. IMO, the relationship between k8s
> and cloudstack should be similar to application and os. It probably
> not a good idea to make your OS to be aware of any specific
> applications so IMHO I don’t think k8s should be native to CloudStack.
> It makes more sense to provide some generic services that many
> applications can take advantages of. Some generic resource grouping
> service makes sense so a group of VMs, baremetal machines or network
> can be treated as a single entity. Some life cycle management will be
> necessary for these entities too. We can deploy k8s, swarm, dcos or
> even non-container specific services on top of CloudStack. The k8s is
> changing fast. One single tenant installation may need more than one
> VM group and may actually requires more (k8s federation). It will be a
> struggle to be in sync if we try to bring k8s specific knowledge into 
> cloudstack.
>
> Regards,
>
>
> --
> Lianghwa Jou
> VP Engineering, Accelerite
> email: lianghwa@accelerite.com
>
>
>
>
>
> On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
>
>
> I agree with some good views Will has shared and I also agree to
> the concerns raised by Wido and Eric. IMO we need balance of staying
> relevant/add new features vs stability of CloudStack and take
> corrective action if needed. We have two good examples for both. When
> SDN was hot technology CloudStack ended up with bunch of SDN controller 
> integrations.
> Few years later, now CloudStack is carrying baggage with no
> maintainers for those plugins, with probably not many of CloudStack users 
> needing overlays.
> On the other hand, other than attempt to liaison with ETSI for NFV no
> effort was done. OpenStack has become de-facto for NFV. Now for
> OpenStack, arguably NFV has become larger use case than cloud it self.
> I concur with Will’s point that with minimal viable solution that does
> not change the core of CloudStack, and can keep CloudStack relevant is
> worth to be taken in.
>
> Will,
>
> To your question of how different is from ShapeBlue’s container
> service, its design, implementation and API semantics etc remain same.
> ShapeBlue’s container service was true drop in plug-in to CloudStack,
> with this proposal I am trying to re-work to make it a core CloudStack
> pluggable service which is part of CloudStack.
>
> Key concepts that this proposal is trying to add
>
> - add notion of ‘container cluster’ as a first class entity in
> CloudStack. Which is bacially collection of other CloudStack resources
> (like VM’s, networks, public ip, network rules etc)
> - life cycle operation to manage ‘container cluster’ like
> create, delete, start, stop, scale-up, scale-down, heal etc
> - orchestrate container orchestrator control plane on top of
> provisioned resources
>
> At-least for k8s (which is what this proposal is targeting),
> integration with k8s is

[GitHub] cloudstack pull request #1936: [CLOUDSTACK-9773] API: don't break API output...

[marcaurele]

GitHub user marcaurele opened a pull request:

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

[CLOUDSTACK-9773] API: don't break API output with non-printable characters

Signed-off-by: Marc-Aurèle Brothier 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/exoscale/cloudstack CLOUDSTACK-9773

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1936.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1936


commit 215d8f6752219933e6b93f4f0c8579086f6ddcf9
Author: Marc-Aurèle Brothier 
Date:   2017-02-06T15:18:23Z

API: don't break API output with non-printable characters

Signed-off-by: Marc-Aurèle Brothier 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [PROPOSAL] add native container orchestration service

[Will Stevens]

​My understanding is that what Paul is talking about is what is already
built and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer



On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani <
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. The
> conversation was specifically about adding support for container
> orchestrators. You are talking about provisioning a group of VMs. Although,
> this is something I think several Cloudstack users have requested before
> and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus 
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of
> Clusters of VMs to CloudStack.  These may be for databases, containers or
> anything else that needs 'clusters' of compute. Self-healing and
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container
> service piece.  If/when the 'cluster' part of that work is added into
> CloudStack, the k8s specific pieces can be used by anyone who wants to,
> alternatively they could be used for reference in order to create another
> types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
>
> > I think that is covered in this proposal. There is nothing k8s
> > specific in this integration (from what I understand), all the k8s
> > details are passed in via the cloud-init configuration after the cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > wrote:
> >
> >
> > There are many container orchestrators. Those container orchestrators
> > are happy to run on any VMs or bare metal machines. K8s is just one of
> > them and there will be more in the future. It may not be a good idea
> > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > and cloudstack should be similar to application and os. It probably
> > not a good idea to make your OS to be aware of any specific
> > applications so IMHO I don’t think k8s should be native to CloudStack.
> > It makes more sense to provide some generic services that many
> > applications can take advantages of. Some generic resource grouping
> > service makes sense so a group of VMs, baremetal machines or network
> > can be treated as a single entity. Some life cycle management will be
> > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > even non-container specific services on top of CloudStack. The k8s is
> > changing fast. One single tenant installation may need more than one
> > VM group and may actually requires more (k8s federation). It will be a
> > struggle to be in sync if we try to bring k8s specific knowledge into
> cloudstack.
> >
> > Regards,
> >
> >
> > --
> > Lianghwa Jou
> > VP Engineering, Accelerite
> > email: lianghwa@accelerite.com
> >
> >
> >
> >
> >
> > On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
> >
> >
> > I agree with some good views Will has shared and I also agree to
> > the concerns raised by Wido and Eric. IMO we need balance of staying
> > relevant/add new features vs stability of CloudStack and take
> > corrective action if needed. We have two good examples for both. When
> > SDN was hot technology CloudStack ended up with bunch of SDN controller
> integrations.
> > Few years later, now CloudStack is carrying baggage with no
> > maintainers for those plugins, with probably not many of CloudStack
> users needing overlays.
> > On the other hand, other than attempt to liaison with ETSI for NFV no
> > effort was done. OpenStack has become de-facto for NFV. Now for
> > OpenStack, arguably NFV has become larger use case than cloud it self.
> > I concur with Will’s point that with minimal viable solution that does
> > not change the core of CloudStack, and can keep CloudStack relevant is
> > worth to be taken in.
> >
> > Will,
> >
> > To your question of how different is from ShapeBlue’s container
> > service, its design, implementation and API semantics etc remain same.
> > ShapeBlue’s container service was true drop in plug-in to CloudStack,
> > with this proposal I am trying to re-work to make it a core CloudStack
> > pluggable service which is part of CloudStack.
> >
> > Key concepts that this proposal is trying to add
> >
> > - add notion of ‘container cluster’ as a 

[GitHub] cloudstack issue #1913: CLOUDSTACK-9752: [Vmware] Optimization of volume att...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1913
  
@sateesh-chodapuneedi @SudharmaJain Can you provide your feedback? I think 
you guys worked on a similar fix


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1934: [CLOUDSTACK-9772] Template: perform a HEAD request t...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1934
  
Trillian test result (tid-805)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 30524 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1934-t805-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Intermitten failure detected: /marvin/tests/smoke/test_templates.py
Test completed. 47 look ok, 2 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 345.56 | 
test_privategw_acl.py
test_04_extract_template | `Error` | 5.09 | test_templates.py
test_03_delete_template | `Error` | 5.09 | test_templates.py
test_01_vpc_site2site_vpn | Success | 160.59 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 66.24 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 251.04 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 277.10 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 530.30 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 522.63 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1418.66 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 543.48 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 750.07 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1286.15 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 156.47 | test_volumes.py
test_08_resize_volume | Success | 156.38 | test_volumes.py
test_07_resize_fail | Success | 161.45 | test_volumes.py
test_06_download_detached_volume | Success | 156.43 | test_volumes.py
test_05_detach_volume | Success | 155.74 | test_volumes.py
test_04_delete_attached_volume | Success | 151.25 | test_volumes.py
test_03_download_attached_volume | Success | 156.33 | test_volumes.py
test_02_attach_volume | Success | 124.15 | test_volumes.py
test_01_create_volume | Success | 716.59 | test_volumes.py
test_03_delete_vm_snapshots | Success | 275.22 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 95.77 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 163.77 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 267.73 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.03 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.65 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.25 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 41.02 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.13 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 125.86 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 125.83 | test_vm_life_cycle.py
test_02_start_vm | Success | 10.17 | test_vm_life_cycle.py
test_01_stop_vm | Success | 40.34 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 40.55 | test_templates.py
test_08_list_system_templates | Success | 0.05 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.05 | test_templates.py
test_02_edit_template | Success | 90.11 | test_templates.py
test_01_create_template | Success | 45.45 | test_templates.py
test_10_destroy_cpvm | Success | 136.60 | test_ssvm.py
test_09_destroy_ssvm | Success | 168.61 | test_ssvm.py
test_08_reboot_cpvm | Success | 101.50 | test_ssvm.py
test_07_reboot_ssvm | Success | 133.49 | test_ssvm.py
test_06_stop_cpvm | Success | 131.67 | test_ssvm.py
test_05_stop_ssvm | Success | 133.83 | test_ssvm.py
test_04_cpvm_internals | Success | 1.22 | test_ssvm.py
test_03_ssvm_internals | Success | 3.45 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.13 | test_ssvm.py
test_01_list_sec_storage_vm | Success | 0.13 | test_ssvm.py
test_01_snapshot_root_disk | Success | 11.12 | test_snapshots.py
test_04_change_offering_small | Success | 239.69 | test_service_offerings.py
test_03_delete_service_offering | Success | 0.04 | test_service_offerings.py
test_02_edit_service_offering | Success | 0.06 | test_service_offerings.py
test_01_create_service_offering | Success | 0.13 | test_service_offerings.py
test_02_sys_template_ready | Success | 0.13 | test_secondary_storage.py
test_01_sys_vm_start | Success | 0.18 | test_secondary_storage.py
test_09_reboot_router | Success | 35.30 | test_routers.py
test_08_start_router | Success | 30.30 | test_routers.py
test_07_st

[GitHub] cloudstack pull request #775: CLOUDSTACK-8805: Domains become inactive autom...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge proces...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
Hi @karuturi,
On Vmware, step 2 reduces tasks sent to hypervisor by sending only one task 
which actually deletes vm snapshots and the vm itself instead of sending one 
for each vm snapshot plus the one for the vm. For other hypervisors, it would 
work the same. I refactored this PR adding tag [Vmware] on title too.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge proces...

[nvazquez]

Github user nvazquez commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
@karuturi regarding tests done, we've compared the number of delete tasks 
sent to Vmware hypervisor on expunging a vm with `N` vm snapshots before and 
after this optimization, reducing from `N+1` tasks to only `1`. Is a marvin 
test required for this case?

Thanks


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1913: CLOUDSTACK-9752: [Vmware] Optimization of volume att...

[SudharmaJain]

Github user SudharmaJain commented on the issue:

https://github.com/apache/cloudstack/pull/1913
  
@nvazquez I think in case if connection to vcenter fails there are changes 
as the disk may get created on vcenter. In such case we may need to remove the 
vmdk. we can improve the logic to search vmdk in specific location of data 
store and reduce the delay. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [PROPOSAL] add native container orchestration service

[Paul Angus]

Will is 100% correct.  As I mentioned the Title is misleading.  However, Murali 
did clarify in his explanation; this is really about vm cluster orchestration.




From: Will Stevens 
Sent: 6 Feb 2017 22:54
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service

​My understanding is that what Paul is talking about is what is already
built and IS what the thread is talking about.​

*Will STEVENS*
Lead Developer



On Mon, Feb 6, 2017 at 2:29 PM, Rajesh Ramchandani <
rajesh.ramchand...@accelerite.com> wrote:

> Hi Paul - I think this is different from what the thread was about. The
> conversation was specifically about adding support for container
> orchestrators. You are talking about provisioning a group of VMs. Although,
> this is something I think several Cloudstack users have requested before
> and we should propose a solution to this.
>
> Raj
>
> 
> From: Paul Angus 
> Sent: Monday, February 6, 2017 11:16:41 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] add native container orchestration service
>
> #WhatHeSaid
>
> The title is misleading.  The proposal is purely to add the notion of
> Clusters of VMs to CloudStack.  These may be for databases, containers or
> anything else that needs 'clusters' of compute. Self-healing and
> autoscaling are logical next steps to be added.
>
> Those guys at ShapeBlue have open-sourced their whole k8s container
> service piece.  If/when the 'cluster' part of that work is added into
> CloudStack, the k8s specific pieces can be used by anyone who wants to,
> alternatively they could be used for reference in order to create another
> types of cluster.  (or ignored completely).
>
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Will Stevens [mailto:williamstev...@gmail.com]
> Sent: 31 January 2017 13:26
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] add native container orchestration service
>
> s/cloud-init/cloud-config/
>
> On Jan 31, 2017 7:24 AM, "Will Stevens"  wrote:
>
> > I think that is covered in this proposal. There is nothing k8s
> > specific in this integration (from what I understand), all the k8s
> > details are passed in via the cloud-init configuration after the cluster
> has been provisioned.
> >
> > On Jan 31, 2017 3:06 AM, "Lianghwa Jou" 
> > wrote:
> >
> >
> > There are many container orchestrators. Those container orchestrators
> > are happy to run on any VMs or bare metal machines. K8s is just one of
> > them and there will be more in the future. It may not be a good idea
> > to make CloudStack to be k8s aware. IMO, the relationship between k8s
> > and cloudstack should be similar to application and os. It probably
> > not a good idea to make your OS to be aware of any specific
> > applications so IMHO I don’t think k8s should be native to CloudStack.
> > It makes more sense to provide some generic services that many
> > applications can take advantages of. Some generic resource grouping
> > service makes sense so a group of VMs, baremetal machines or network
> > can be treated as a single entity. Some life cycle management will be
> > necessary for these entities too. We can deploy k8s, swarm, dcos or
> > even non-container specific services on top of CloudStack. The k8s is
> > changing fast. One single tenant installation may need more than one
> > VM group and may actually requires more (k8s federation). It will be a
> > struggle to be in sync if we try to bring k8s specific knowledge into
> cloudstack.
> >
> > Regards,
> >
> >
> > --
> > Lianghwa Jou
> > VP Engineering, Accelerite
> > email: lianghwa@accelerite.com
> >
> >
> >
> >
> >
> > On 1/29/17, 11:54 PM, "Murali Reddy"  wrote:
> >
> >
> > I agree with some good views Will has shared and I also agree to
> > the concerns raised by Wido and Eric. IMO we need balance of staying
> > relevant/add new features vs stability of CloudStack and take
> > corrective action if needed. We have two good examples for both. When
> > SDN was hot technology CloudStack ended up with bunch of SDN controller
> integrations.
> > Few years later, now CloudStack is carrying baggage with no
> > maintainers for those plugins, with probably not many of CloudStack
> users needing overlays.
> > On the other hand, other than attempt to liaison with ETSI for NFV no
> > effort was done. OpenStack has become de-facto for NFV. Now for
> > OpenStack, arguably NFV has become larger use case than cloud it self.
> > I concur with Will’s point that with minimal viable solution that does
> > not change the core of CloudStack, and can keep CloudStack relevant is
> > worth to be taken in.
> >
> > Will,
> >
> > To your question of how different is from ShapeBlue’s container
> > service, its design, implementation and API semantic