Re: [ASK][DISCUSS] Adding support for a new block-storage based primary storage

[Tutkowski, Mike]

Hi Rohit,

I’m guessing in your case (since you say this storage is similar to RBD) that 
it would, as you say, be simpler to make changes to 
CloudStackPrimaryDataStoreLifeCycleImpl to support this new storage type.

Of course, this then adds yet one more storage type that that particular class 
is responsible for, thus complicating its code.

If making those changes in CloudStackPrimaryDataStoreLifeCycleImpl doesn’t 
complicate that code too much more, then it’s probably OK. However, I really 
like the approach of being able to write a new plug-in per storage type (as you 
say, as is done with SolidFire, Datera, and CloudByte). In this case, you don’t 
have to worry so much about breaking storage types that already are working 
and/or complicating the logic of CloudStackPrimaryDataStoreLifeCycleImpl to 
support another storage type.

I think the reason CloudStackPrimaryDataStoreLifeCycleImpl supports multiple 
storage types in the first place probably dates back to when CloudStack’s 
storage component was first modularized in such a way that it could support 
storage plug-ins (back in 2012 and 2013 for CloudStack 4.1). At this time, I 
believe Edison Su took the originally supported storage types and put them in 
CloudStackPrimaryDataStoreLifeCycleImpl (others have probably added new storage 
types in here, as well, over the years). Then I came along and started writing 
a completely separate storage plug-in for SolidFire for CloudStack 4.2 (which 
Edison’s new storage architecture for 4.1 began to enable). CloudByte and 
Datera liked the separate storage plug-in approach, so they went the same route 
in this regard as I did with SolidFire.

So, anyways, those are some of my thoughts on the matter.

Talk to you later!
Mike

From: Rohit Yadav 
Date: Tuesday, June 23, 2020 at 2:14 AM
To: "dev@cloudstack.apache.org" 
Cc: "Tutkowski, Mike" , Wido den Hollander 
, Gabriel Beims Bräscher , Will Stevens 

Subject: [ASK][DISCUSS] Adding support for a new block-storage based primary 
storage

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.


All, /cc Mike, Wido, Gabriel, Will

Support for some primary storage pool types (such as RBD, Gluster, CLVM, VMFS) 
is added in the default datastore provider 
(CloudStackPrimaryDataStoreLifeCycleImpl) while for others (such as Solidfire, 
Datera, CloudByte etc) is implemented in its own lifecycle/driver.

I'm trying to write a design doc for adding support for a block-storage based 
volume storage similar to RBD (primarily for KVM) and I looked into the storage 
sub-system [1] design doc as well as how RBD[2] support was added and I'm 
evaluating pros and cons of adding the support by (a) extending the default 
volume provider versus (b) writing a new volume storage driver/plugin, and both 
would require adding handlers in libvirt/kvm server resource. Approach #a would 
be simpler to implement than #b based on code investigation, what are your 
thoughts and advice on this? Thanks.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Storage+subsystem+2.0
[2] 
https://github.com/apache/cloudstack/commit/406fd95d87bfcdbb282d65589ab1fb6e9fd0018a



Regards.

rohit.ya...@shapeblue.com
www.shapeblue.com
@shapeblue

Re: Managed Storage and HA

[Tutkowski, Mike]

I am thinking you would make the ListVolumeStats API call to the SF cluster 
from a management server because we know that management servers should have 
access to the management network of the SF cluster. I know some KVM hosts might 
have access to the management network of the SF cluster that supports their 
volumes, but they don't have to: KVM hosts (and hypervisor hosts in general) 
only need access to the storage network of the SF cluster that supports their 
volumes. If the agent happened to be running on a KVM host that only has access 
to the storage network, then this agent can't make the ListVolumeStats API 
call. As such, I think the ListVolumeStats API call should be executed from a 
management server.

You are correct that the volumes_details tables contains the ID of a SolidFire 
volume.

I don't know all of the ways a volume can transition from the Ready state to 
some other state. I would not rely on the volume's state in the DB to determine 
if a VM is having trouble accessing a volume.

On 6/8/20, 2:47 PM, "Sven Vogel"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi Paul, Hi Mike, Hi Syed,

@Paul
> Doesn’t the same problem exist with that?  If the agent dies, then the 
fake volume will stop being updated but the VMs would still be running.

Do you mean we don’t know if a machine is running and get an false 
positive? I think about if we had only one fake volume and if they are not 
there so we would get an fencing of the host and kill all machines. Maybe the 
other volumes are accessible.

I see different challenges.

1. SF uses normally a storage network so with that if the management 
network is down don’t means the volumes are not accessible.
2. A Fake volume can produce false positives maybe this one is due too any 
reason will not accessible but the other ones can be achieved

@Mike

> Since you know which (SolidFire) volumes are connected to a particular 
KVM host, I would think you could just use the ListVolumeStats API (described 
below) from a management server to determine if there is disk activity to any 
of those volumes.

You mean the work would be done not from the Agent but from the management. 
You mean we should periodically check the "ListVolumeStats“ on the Solidfire 
from the Management Server and know if they are active.

What I see is that in the „volume_details“ table are all SF volumes are 
listed. Right? They are connected with the „volumes“ table and there I will 
finde the „instance_id“. Now there are two ways. Find about the „vm_instance“ 
table the if the instance is „running“, I think this is important and „host_id“

I don’t know if the „volumes“ table „ready“ state is useful. This will give 
us a „ready“ state but does not mean its active. I hope I am correct.

@Paul
If this is thinkable where is a best way to implement it that it works. I 
mean what I need to enable that i know HA is working but lacking on the storage 
heartbeat.

1. How I need to configure HA that it will work?
2. I read the documentation from Rohit and found that he wrote "For the 
initial release, only KVM with NFS storage will be supported. However, the 
storage check component will be implemented in a modular fashion allowing for 
checks using other storage platforms(e.g. Ceph) in the future.“ Where is a good 
way In the code to start so won’t implement it wrong and lets more focused on 
finalizing? Maybe you can clarify it a little bit.

Cheers Sven



__

Sven Vogel
Lead Cloud Solution Architect

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, Tassilo Möschke
Registergericht: Leipzig HRB 9065

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 

Re: Managed Storage and HA

[Tutkowski, Mike]

Since you know which (SolidFire) volumes are connected to a particular KVM 
host, I would think you could just use the ListVolumeStats API (described 
below) from a management server to determine if there is disk activity to any 
of those volumes.

On 6/8/20, 10:32 AM, "Syed Ahmed"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Yeah that's true. I wonder if we could get iscsi information from the
Solidfire API that way the agent is just responsible for the iscsi login of
the fake volume and then we just monitor the API for connect time

On Mon, Jun 8, 2020 at 12:17 PM Paul Angus  wrote:

> Doesn’t the same problem exist with that?  If the agent dies, then the
> fake volume will stop being updated but the VMs would still be running.
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Syed Ahmed 
> Sent: 08 June 2020 17:14
> To: dev@cloudstack.apache.org
> Subject: Re: Managed Storage and HA
>
> My suggestion would be to use a "fake" volume for each host and use that
> to check the activity of a host. The volume can be updated by the agent
> periodically and then we can use the above API from the management server
> to query the volume activity.
>
> On Tue, Jun 2, 2020 at 1:18 PM Tutkowski, Mike 
> wrote:
>
> > Hi Sven,
> >
> > You can use the ListVolumeStats API call (I put in an example request
> > and response below).
> >
> > Since this goes over the management network, though, it's possible if
> > your management network is down, but your storage network is up that
> > this call could fail, but your VMs might still have perfectly good
> > access to their volumes.
> >
> > Talk to you later!
> > Mike
> >
> > Request:
> >
> > {
> >"method": "ListVolumeStats",
> >"params": {
> > "volumeIDs": [1, 2]
> >},
> >"id" : 1
> > }
> >
> > Response:
> >
> > {
> > "id": 1,
> > "result": {
> > "volumeStats": [
> > {
> > "accountID": 1,
> > "actualIOPS": 14,
> > "asyncDelay": null,
> > "averageIOPSize": 13763,
> > "burstIOPSCredit": 0,
> > "clientQueueDepth": 0,
> > "desiredMetadataHosts": null,
> > "latencyUSec": 552,
> > "metadataHosts": {
> > "deadSecondaries": [],
> > "liveSecondaries": [],
> > "primary": 5
> > },
> > "nonZeroBlocks": 10962174,
> > "normalizedIOPS": 34,
> > "readBytes": 747306804224,
> > "readBytesLastSample": 0,
> > "readLatencyUSec": 0,
> > "readLatencyUSecTotal": 11041939920,
> > "readOps": 19877559,
> > "readOpsLastSample": 0,
> > "samplePeriodMSec": 500,
> > "throttle": 0,
> > "timestamp": "2020-06-02T17:14:35.444789Z",
> > "unalignedReads": 2176454,
> > "unalignedWrites": 1438822,
> > "volumeAccessGroups": [
> > 1
> > ],
> > "volumeID": 1,
> > "volumeSize": 2147483648000,
> > "volumeUtilization": 0.002267,
> > "writeBytes": 3231402834432,
> > "writeBytesLastSample": 106496,
> > "writeLatencyUSec": 552,
> > "writeLatencyUSecTotal"

Re: Managed Storage and HA

[Tutkowski, Mike]

Hi Sven,

You can use the ListVolumeStats API call (I put in an example request and 
response below).

Since this goes over the management network, though, it's possible if your 
management network is down, but your storage network is up that this call could 
fail, but your VMs might still have perfectly good access to their volumes.

Talk to you later!
Mike

Request:

{
   "method": "ListVolumeStats",
   "params": {
"volumeIDs": [1, 2]
   },
   "id" : 1
}

Response:

{
"id": 1,
"result": {
"volumeStats": [
{
"accountID": 1,
"actualIOPS": 14,
"asyncDelay": null,
"averageIOPSize": 13763,
"burstIOPSCredit": 0,
"clientQueueDepth": 0,
"desiredMetadataHosts": null,
"latencyUSec": 552,
"metadataHosts": {
"deadSecondaries": [],
"liveSecondaries": [],
"primary": 5
},
"nonZeroBlocks": 10962174,
"normalizedIOPS": 34,
"readBytes": 747306804224,
"readBytesLastSample": 0,
"readLatencyUSec": 0,
"readLatencyUSecTotal": 11041939920,
"readOps": 19877559,
"readOpsLastSample": 0,
"samplePeriodMSec": 500,
"throttle": 0,
"timestamp": "2020-06-02T17:14:35.444789Z",
"unalignedReads": 2176454,
"unalignedWrites": 1438822,
"volumeAccessGroups": [
1
],
"volumeID": 1,
"volumeSize": 2147483648000,
"volumeUtilization": 0.002267,
"writeBytes": 3231402834432,
"writeBytesLastSample": 106496,
"writeLatencyUSec": 552,
"writeLatencyUSecTotal": 44174792405,
"writeOps": 340339085,
"writeOpsLastSample": 7,
"zeroBlocks": 513325826
},
{
"accountID": 1,
"actualIOPS": 0,
"asyncDelay": null,
"averageIOPSize": 11261,
"burstIOPSCredit": 0,
"clientQueueDepth": 0,
"desiredMetadataHosts": null,
"latencyUSec": 0,
"metadataHosts": {
"deadSecondaries": [],
"liveSecondaries": [],
"primary": 5
},
"nonZeroBlocks": 28816654,
"normalizedIOPS": 0,
"readBytes": 778768996864,
"readBytesLastSample": 0,
"readLatencyUSec": 0,
"readLatencyUSecTotal": 7068679159,
"readOps": 14977610,
"readOpsLastSample": 0,
"samplePeriodMSec": 500,
"throttle": 0,
"timestamp": "2020-06-02T17:14:35.445978Z",
"unalignedReads": 890959,
"unalignedWrites": 358758,
"volumeAccessGroups": [
1
],
"volumeID": 2,
"volumeSize": 2147483648000,
"volumeUtilization": 0,
"writeBytes": 8957684071424,
"writeBytesLastSample": 0,
"writeLatencyUSec": 0,
"writeLatencyUSecTotal": 16780712096,
"writeOps": 406101472,
"writeOpsLastSample": 0,
"zeroBlocks": 495471346
}
]
}
}

On 6/2/20, 9:11 AM, "Sven Vogel"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi Paul,

Thanks for the answer and help.

Ok. Secondary Storage is no good solution what I understand.

> 1. HAManager
> 2. HighAvailbilityManager
> 3. KVMHAConfig


which of the three should we expand and which one should be active?

@Mike did you know somethings like that if there is a check of volume 
activity?
Maybe we can poll the API but I think this will be a massive polling 
(overload) if we poll for each volume.
Ah the moment I don’t have any idea how this could work.

Cheers

Sven


__

Sven Vogel
Lead Cloud Solution Architect

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, Tassilo Möschke
Registergericht: Leipzig HRB 9065

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 

Re: [VOTE] Primate as modern UI for CloudStack

[Tutkowski, Mike]

+1


From: Rohit Yadav 
Sent: Monday, October 7, 2019 5:31:15 AM
To: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Subject: [VOTE] Primate as modern UI for CloudStack

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




All,

The feedback and response has been positive on the proposal to use Primate as 
the modern UI for CloudStack [1] [2]. Thank you all.

I'm starting this vote (to):

  *   Accept Primate codebase [3] as a project under Apache CloudStack project
  *   Create and host a new repository (cloudstack-primate) and follow Github 
based development workflow (issues, pull requests etc) as we do with CloudStack
  *   Given this is a new project, to encourage cadence until its feature 
completeness the merge criteria is proposed as:
 *   Manual testing against each PR and/or with screenshots from the author 
or testing contributor, integration with Travis is possible once we get JS/UI 
tests
 *   At least 1 LGTM from any of the active contributors, we'll move this 
to 2 LGTMs when the codebase reaches feature parity wrt the existing/old 
CloudStack UI
 *   Squash and merge PRs
  *   Accept the proposed timeline [1][2] (subject to achievement of goals wrt 
Primate technical release and GA)
 *   the first technical preview targetted with the winter 2019 LTS release 
(~Q1 2020) and release to serve a deprecation notice wrt the older UI
 *   define a release approach before winter LTS
 *   stop taking feature FRs for old/existing UI after winter 2019 LTS 
release, work on upgrade path/documentation from old UI to Primate
 *   the first Primate GA targetted wrt summer LTS 2020 (~H2 2019), but 
still ship old UI with a final deprecation notice
 *   old UI codebase removed from codebase in winter 2020 LTS release

The vote will be up for the next two weeks to give enough time for PMC and the 
community to gather consensus and still have room for questions, feedback and 
discussions. The results to be shared on/after 21th October 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)

[1] Primate Proposal:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal%3A+CloudStack+Primate+UI

[2] Email thread reference:
https://markmail.org/message/z6fuvw4regig7aqb

[3] Primate repo current location: https://github.com/shapeblue/primate


Regards,

Rohit Yadav

Software Architect, ShapeBlue

https://www.shapeblue.com

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

SolidFire CloudStack 4.11.3 and VMWare 6.5

[Tutkowski, Mike]

Can you take a look in the cloud.host table and see if the IQN of each of the 
relevant hosts is populated in the url cell?

If it is not, you might have to run the force reconnect command on each 
applicable host (this is a CloudStack command).

From: christian.nieph...@zv.fraunhofer.de 
Sent: Wednesday, September 4, 2019 9:19 AM
To: us...@cloudstack.apache.org
Cc: christian.kir...@zv.fraunhofer.de
Subject: SolidFire CloudStack 4.11.3 and VMWare 6.5

Hi,
we are currently doing a PoC with SolidFire and CloudStack and trying to figure 
out if it’s a fitting solution for our use cases.

But I am stuck at the point when CloudStack tries to create a VM on the solid 
fire storage.
I can see that it has already copied the template to a SolidFire Volume but 
then the error message "Not all hosts in the compute cluster support iSCSI.” 
appears in the logs.

On the ESXi I have created a iSCSI HBA and attached it to a VMKernel adapter, 
is there anything else to do?
Is there any documentation for the setup? I have only found the youtube videos 
by Mike, but they does not focus on the vsphere setup part.


Regards Christian

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

[Tutkowski, Mike]

Congratulations, Bobby!


From: Paul Angus 
Sent: Tuesday, July 16, 2019 3:12:51 AM
To: priv...@cloudstack.apache.org; dev@cloudstack.apache.org; 
us...@cloudstack.apache.org
Subject: [ANNOUNCE] Bobby (Boris Stoyanov) has joined the PMC

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




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

Re: [ANNOUNCE] Sven Vogel has joined the PMC

[Tutkowski, Mike]

Congratulations, Sven!


From: Paul Angus 
Sent: Saturday, July 13, 2019 9:44:47 AM
To: priv...@cloudstack.apache.org; dev@cloudstack.apache.org; 
us...@cloudstack.apache.org
Subject: [ANNOUNCE] Sven Vogel has joined the PMC

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




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

Re: [ANNOUNCE] Andrija Panic has joined the PMC

[Tutkowski, Mike]

Congratulations, Andrija!


From: Paul Angus 
Sent: Saturday, July 13, 2019 9:02:57 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; 
priv...@cloudstack.apache.org
Subject: [ANNOUNCE] Andrija Panic has joined the PMC

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




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: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

[Tutkowski, Mike]

Congratulations, Gabriel!


From: Paul Angus 
Sent: Saturday, July 13, 2019 10:01 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; 
priv...@cloudstack.apache.org
Subject: [ANNOUNCE] Gabriel Beims Bräscher has joined the PMC

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




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

Re: Doubt about the development environment and Devcloud

[Tutkowski, Mike]

I don't have current info on how to set up a dev environment (someone else can 
provide this pretty easily, I suspect) as I haven't been writing CloudStack 
code the past six months, but I do have a video link you might be interested in 
regarding building plug-ins in CloudStack (from a presentation I gave at the 
CloudStack Collab Conf in Seville in 2016):

https://www.youtube.com/watch?v=J9Xc6muzaAk=PLqOXKM0Bt13DFnQnwUx8ZtJzoyDV0Uuye=32=116s

On 7/1/19, 11:29 AM, "José Flauzino"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi, I'm new to the mailing list and it's my first question.

I'm masters student in computer science at the Federal University of
Paraná (Brazil) and my research proposal involves developing a
CloudStack plug-in.

My initial difficulty is to deploy the complete environment so that I
have the CloudStack source code in an IDE (e.g., Eclipse) and is able to
create VMs using this same deploy.

At the moment, following the documentation [1], I can run CloudStack in
Eclipse and I even started to develop a test plugin following this here
[2]. However, only with this I can not to run VMs.

Reading the documentation I understood that to do this I need of
Devcloud, but I could not get it because the links (1 [3],2 [4]) I found
are broken and the DIY tutorials [5] I found are old and did not work
for me.

So to be more specific I would ask this questions:

1 - Has anyone available a OVA or QCOW2 image, or newer DIY tutorial?

2 - Is it possible to run cloudstack-agent from a CloudStack deployment
that runs using source code (without packaging) for me to use as a host
(hypervisor)? If so, how can I do this?

PS: After I can run CloudStack the way I need it, I'm going to evaluate
the feasibility of the implementation I want to do, and if I find it to
be feasible, I send a proposal here on the mailing list to see if it's
in the community's interest.

Any suggestions are welcome!

Thanks.
--
JOSÉ WILSON VIEIRA FLAUZINO
M.Sc. student in Informatics
 Department of Informatics
 Federal University of Paraná - Brazil
http://www.inf.ufpr.br/jwvflauzino/

* Add to Phrasebook

* No word lists for English -> Portuguese...

* Create a new word list...

* Copy

* Add to Phrasebook

* No word lists for English -> Portuguese...

* Create a new word list...

* Copy



Links:
--
[1]

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+Eclipse+With+CloudStack
[2]

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+Development
[3] http://home.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova
[4] http://people.apache.org/~sebgoa/devcloud2.ova
[5] https://rohityadav.cloud/blog/devcloud/

Re: CCC NA19 - talk selection

[Tutkowski, Mike]

I can help with this, Giles.


From: Paul Angus 
Sent: Monday, May 20, 2019 3:46:37 AM
To: priv...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: RE: CCC NA19 - talk selection

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Thanks for taking this on Giles,  I'm happy to help out.

From: Giles Sirett 
Sent: 20 May 2019 10:45
To: dev@cloudstack.apache.org
Cc: priv...@cloudstack.apache.org
Subject: CCC NA19 - talk selection

Hi all
The CFP for Cloudstack Collab  (http://us.cloudstackcollab.org/) has now closed.
We've had a good number of submissions which now need to be sifted and selected

In previous years, we've done this by getting a small  "selection committee" 
together. My suggestion is that we do the same this year

So, we need some volunteers

Please, can anybody who like to help with this step forward now!

We have to get the agenda together by 3 June, so time is tight


Kind regards
Giles


giles.sir...@shapeblue.com
www.shapeblue.com
@shapeblue




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

Re: Ansible 2.8: CloudStack related changes

[Tutkowski, Mike]

Thanks, Rene, for all of the work you've done for CloudStack!


From: Rene Moser 
Sent: Thursday, May 16, 2019 1:42 AM
To: us...@cloudstack.apache.org; dev
Subject: Ansible 2.8: CloudStack related changes

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi all

As announced previously in autumn 2018, I am ending my active
maintenance for the CloudStack Ansible integration with the 2.8 release.

It started as PoC during a weekend at a Swiss Linux hackers event
"Turrican Days" in autumn 2014 and turned into "thing" I have spent many
nights with. Take care of it.

The modules are in best conditions: Cloudstack is one of a few Ansible
integrations without any failing sanity checks. Special thanks goes to
David Passante who brought all the docs in shape!

We have automated integration tests based on a simulator docker setup
[1] currently running Cloudstack 4.11.2. The integration test code
coverage [2] is at >85%.

There are currently (only) 2 more members in the CloudStack team [3] in
Ansible.

Thanks again for all the support and appreciation I have received over
the years.

Ansible v2.8.0 is going to be released with the following, CloudStack
related changes, thanks for all the contributors:

David Passante (18):
  Cloudstack: fix support for some VPC service capabilities (#45727)
  cs_account: Implement role parameter support (#46166)
  cs_account: add ability to bind accounts to LDAP (#46219)
  Cloudstack: New module cs_vlan_ip_range (#51597)
  cloudstack: streamline modules doc (#52509)
  cloudstack: streamline modules doc (part 2) (#52730)
  cloudstack: streamline modules doc (part 3) (#53412)
  cs_iso: fix missing param "is_public" (#53740)
  cs_network_offering: Add choice list for supported_services in
arg_spec (#53901)
  cloudstack: streamline modules doc (part 4) (#53874)
  cs_volume: add volumes extraction and upload features (#54111)
  cs_instance_facts: add a "nic" fact to return VM networking
information (#54337)
  cs_service_offering: update params in arg spec and documentation
(#54511)
  cs_network_offering: add a for_vpc parameter (#54551)
  cloudstack: streamline modules doc (part 5) (#54523)
  cs_service_offering: Implement customizable compute offers (#54597)
  cloudstack: streamline modules doc (part 6) (#54641)
  cs_vlan_ip_range: Update return values documentation (#54677)

Gregor Riepl (1):
  Cloudstack: Add password reset module (#47931)

Patryk D. Cichy (5):
  Add new Cloudstack module cs_image_store (#53617)
  Add new CloudStack module cs_physical_network (#54098)
  Add a new CloudStack module - cs_traffic_type (#54451)
  Enable adding VLAN IP ranges for Physical Networks (#54576)
  Proper handling of lower case name for InternalLbVm Service
Provider (#55087)

Rene Moser (13):
  cs_loadbalancer_rule_member: fix error handling (#46012)
  cs_instance: fix host migration without volume (#46115)
  cs_instance: doc: fix typo in examples (#46035)
  cs_staticnat: fix sanity (#46037)
  cs_ip_address: use query_api, fixes error handling (#46034)
  cs_resourcelimit: use query_api for error handling (#46036)
  cs_ip_address: fix vpc and network mutually exclusive (#47846)
  cs_network_acl_rule: fix doc and sanity (#47835)
  cs_template: fix KeyError on state=extracted (#48675)
  cs_instance: fix typos in defaults for ip/ip6_ipaddress (#49064)
  cs_physical_network: use name as param for network (#54602)
  cloudstack: fix E326 (#54657)

This will be my last announcement and I most probably leaving the
cloudstack mailing lists in the next couple of days.

Best wishes
René

[1] https://github.com/ansible/cloudstack-test-container
[2]
https://codecov.io/gh/ansible/ansible/tree/devel/lib/ansible/modules/cloud/cloudstack
[3]
https://github.com/ansible/ansible/blob/0e0735f10ecb64634a4a1c9ac78a36743295417d/.github/BOTMETA.yml#L1471

Re: Where to start to reuse API integration tests as functional test from CS codebase?

[Tutkowski, Mike]

I don't know if this video will be useful to you, but I gave a few 
presentations on Marvin over the years. Here is one of them:

https://www.youtube.com/watch?v=N_eKBA_TeOs=PLqOXKM0Bt13DFnQnwUx8ZtJzoyDV0Uuye=41=39s

On 4/10/19, 9:42 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi Peter,

The documentation is here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python

but it's not the easiest thing in the world to follow ☹

In summary:

- we have created a CloudStack specific plugin for the nosetests framework 
which is called Marvin.
- once you setup a link to a CloudStack repo as you would to install the 
CloudStack management server, you should be able to yum/apt install 
cloudstack-marvin cloudstack-integration-tests to get everything that you need 
(note Marvin is written for python 2.7)
- you need to edit the setup.cfg to match your environment
- you MAY also need to edit the test_data.py file as well
- to run a single test run:

nosetests --with-marvin --marvin-config=./setup.cfg --hypervisor=vmware -s 
-a tags=advanced $file

You can pass a directory rather than a file.


There is a lot more to it, but this is a start.

Paul.


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




-Original Message-
From: peter.murysh...@zv.fraunhofer.de 
Sent: 10 April 2019 16:23
To: dev@cloudstack.apache.org
Subject: Where to start to reuse API integration tests as functional test 
from CS codebase?

Hi all,

where to to start if I want to run just exactly that part of the CS test 
code base to test the API functionality of a separately deployed instance?

I've found so far this folder:
https://github.com/apache/cloudstack/tree/master/test/integration/component

There are though different scripts in Python, and the folder is a Java 
Maven module?

So how to know which dependencies to I need and where to start?

Is there also a set of regression tests somewhere reflecting bugs fixed in 
course of the time?

thanks in advance
kind regards
Peter

[ANNOUNCE] New Committer: Dennis Konrad

[Tutkowski, Mike]

Hi everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Dennis Konrad to become a committer and I am pleased
to announce that he has accepted.

Please join me in congratulating Dennis on this accomplishment.

Thanks!
Mike

[ANNOUNCE] New Committer: Sven Vogel

[Tutkowski, Mike]

Hi everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Sven Vogel to become a committer and I am pleased
to announce that he has accepted.

Please join me in congratulating Sven on this accomplishment.

Thanks!
Mike

Re: New VP of CloudStack: Paul Angus

[Tutkowski, Mike]

Thanks, everyone! I'm sure Paul will do a fantastic job as VP in the coming 
year.

On 3/13/19, 12:58 PM, "Melanie Desaive"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Wow! Great news! Congratulations Paul!

And thanks a lot to Mike!

All my best wishes to all of you!

Am Montag, den 11.03.2019, 15:16 +0000 schrieb Tutkowski, Mike:
> 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
--
--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 40 50 51 - 62
Fax: 030 / 40 50 51 - 19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin

New VP of CloudStack: Paul Angus

[Tutkowski, Mike]

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: CloudStack Collab Conference Brazil deadline for talk proposals is on 11/02/2019

[Tutkowski, Mike]

Hi everyone,

Just an FYI that we will soon be going through the presentations submitted via 
the CFP for CCC Brazil.

If anyone is interested in participating in the review process, please respond 
to this e-mail.

Thanks!
Mike

On 2/10/19, 7:13 AM, "Rafael Weingärtner"  wrote:

The call for papers (CFP)


for
the first CloudStack Collab Conference Brazil is approaching. If you have
not submitted your talk proposal, you still have time. It is going to be
the first (of many yet to come) that you cannot miss.

You do not need to have the full presentation ready now, all you need three
little things: (i) an interesting title, (ii) a brief description of the
talk to help the committee with the selection process, and (iii) a message
to the reviewing committee saying why your talk is important and
interesting for the cloud ecosystem.

You cannot miss the opportunity to meet the CloudStack community in
Florianopolis. Therefore, if you do not want to be a speaker, you should
come to watch, network, and enjoy not just the conference, but this
picturesque island with perfect beaches, excellent surfing, and amazing
seafood.
--
Rafael Weingärtner

Re: CloudStack Collab Conference Brazil

[Tutkowski, Mike]

Thirty-minute time slots might be a good move. We did that at CCC Budapest in 
2014.

On 2/7/19, 11:23 AM, "Giles Sirett"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Thanks Rafael - looks good

My guess is that the slots may be pre-defined by the event organisers to 
sync with breaks,etc , but if theyre not...

A 50 min is quite a long talk.
If you are expecting a lot of good submissions , 30 minute slots could give 
11 people the opportunity  to talk. From experience, the more speakers, the 
more attendees tend to come along with those speakers



Kind regards
Giles

giles.sir...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




-Original Message-
From: Rafael Weingärtner 
Sent: 07 February 2019 15:26
To: dev 
Subject: Re: CloudStack Collab Conference Brazil

Hey Giles, I will try to answer you inline.

Some questions from me:
>
1. how many speaker slots did you agree for the CCC part of the event (i.e.
> how many talks are required)?
>
As we discussed in the PMC, we ended up with a one day track focused on 
CloudStack. This translates to 7 (50min.) talks. By the number of people I 
talked to, I would say that we will have way more talks than slots :((

>
> 2. You mention CFP closes 11 Febuary, and it seems from the website
> that speakers should submit their talks through
> http://cfp-flp.thedevconf.com.br/  However, there is no track listed
> as CCC. There is a "cloud computing"
> track. Is that the one to use ?  It may make sense to tell people on
> the CCC site which track to use
>

It was in their backlog to fix. I just checked, and it is fixed now.

On Thu, Feb 7, 2019 at 7:10 AM Giles Sirett 
wrote:

> This is great to see Rafael  - well done to you and Mike for getting
> this rolling
>
> Some questions from me:
> 1. how many speaker slots did you agree for the CCC part of the event
> (i.e. how many talks are required)?
> 2. You mention CFP closes 11 Febuary, and it seems from the website
> that speakers should submit their talks through
> http://cfp-flp.thedevconf.com.br/  However, there is no track listed
> as CCC. There is a "cloud computing"
> track. Is that the one to use ?  It may make sense to tell people on
> the CCC site which track to use
>
>
> Kind regards
> Giles
>
> giles.sir...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
>
>
>
>
> -Original Message-
> From: Rafael Weingärtner 
> Sent: 04 February 2019 20:37
> To: dev 
> Cc: users 
> Subject: Re: CloudStack Collab Conference Brazil
>
> Ah Will, sorry for that. I meant to reference the cloudstackcollab
> website, but pressed the send button too fast ;)
>
> On Mon, Feb 4, 2019 at 6:31 PM Will Stevens  wrote:
>
> > We will try to keep the website, http://br.cloudstackcollab.org/, up
> > to date with the details of the event as new information is available.
> > I just figured I would mention that since Rafael didn't mention it in
> his email.
> > :)
> >
> > Cheers,
> >
> > *Will Stevens*
> > Chief Technology Officer
> > c 514.826.0190
> >
> > 
> >
> >
> > On Mon, Feb 4, 2019 at 3:29 PM Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > The first CloudStack Collab Conference Brazil is going to be held in
> > > Florianopolis, in April 2019. It is being run through The Developer
> > > Conference (TDC)  in
> > Brazil.
> > > When you register  you
> > > will be redirected to the *TDC* website.
> > >
> > > TDC runs a series of conferences every year in Brazil
> > > (Florianopolis, São Paulo, and  Porto Alegre). They have been running
> for over a decade now.
> > > TDC conferences cover a broad range of topics, from management 3.0,
> > > software development, Programming languages (Java, Python, Ruby, and
> > > so one), Cloud, and so on. Their average number of attendees is
> > > about ~4000 per TDC event. Therefore, this event is a great
> > > opportunity for enthusiasts, technicians, and vendors to show
> > > themselves and meet with different IT communities.
> > >
> > > For people from our community, it is an opportunity not just to
> > participate
> > > in CloudStack Collab Brazil
> > > <
> > >
> > 

Re: Why CloudStack 5

[Tutkowski, Mike]

That sounds reasonable to me.



From: Rafael Weingärtner 
Sent: Wednesday, January 23, 2019 5:25 PM
To: users
Cc: dev@cloudstack.apache.org
Subject: Re: Why CloudStack 5

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




I would say that it is indeed a solid version. However, version 4.12 by
itself is not breaking anything. Therefore, according to the semantic
versioning, we cannot increase the ‘X’ bit.

It is also interesting to consider that 4.12 has over 188 PRs merged into
it. When we finish, we will probably hit almost 200 PRs. Many new features
were added, and we might have some hidden bugs that were not discovered
yet. Therefore, at least for me, it looks wiser to launch it as a normal
release and work on top of it to create 5.0.0 during July-August 2019. This
should provide 3-6 months of experimentation with the 4.12 version in
production.

On Wed, Jan 23, 2019 at 10:07 PM Tutkowski, Mike 
wrote:

> Is 4.12 a decent candidate to be branded 5.0 or might we be waiting for
> some specific set of backwards-incompatible updates?
>
>
> 
> From: Rafael Weingärtner 
> Sent: Wednesday, January 23, 2019 4:58 PM
> To: dev
> Cc: users
> Subject: Re: Why CloudStack 5
>
> NetApp Security WARNING: This is an external email. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> Hello Ivan,
> Can you provide reasons why not move to a version 5?
>
> To help you, I will provide why I think we should move to 5.0.0 after 4.12.
> Therefore, I would expect this 5.0.0 to be an LTS version as well.
>
> 1. To begin with, technically, we should already be in version 5 if we
> had been following the semantic versioning we say we follow. We broke
> compatibility when Midonet plugin was removed in 4.10, and later, also,
> when public APIs from the IAM projects were removed. You can discuss if
> those features were broken or not, and if they count as a backward
> incompatibility. All in all, it is a removal of public APIs;
> 2. We want to remove the basic network, and with this move, we can
> delete a load of complications and replicated code, which causes more
> burden than anything else;
> 3. There are also some other small details in some PRs, where these
> issues with backward compatibility are holding our code and structure
> improvements. Therefore, a CloudStack 5.0.0 would free us from these
> anchors that we keep dragging around;
> 4. A new database upgrade scheme…. I do not even need to get into this
> topic; all DEVs here know what I am talking about;
> 5. A proper JPA implementation, a real restful API, adopt a standard
> rest framework, and other base technological improvements would be awesome,
> but I would say that they are far from here now. And they will be always
> distant if we keep holding ourselves back.
>
> All in all, to conclude; it is not about the version number and marketing.
> At least for me, I could care less about the number. This is about the
> community being able to adopt new trends, new technology, new methods, and
> understanding that to move on, we need to let somethings go.
>
> On Tue, Jan 22, 2019 at 1:45 AM Ivan Kudryavtsev  >
> wrote:
>
> > I decided whether to write it several weeks thinking about the stones and
> > rotten potatoes, but still decided to do that. Hope it will not raise the
> > stress level.
> >
> > Colleagues and ACS leaders, I would like to initiate the discussion. Why
> go
> > to CS5 rather than stay with 4.XX. Some thoughts are:
> >
> > 1. According to the versioning guide, the first number stands for radical
> > changes like if the community decided to go from current ORM to
> Hibernate.
> > I don't see the capabilities for such changes and there are no intentions
> > for the implementation.
> >
> > 2. I can realize that we 'stuck' with '4.XX' and the marketing can be
> > disappointing from that point of view. Then, OK, let's just skip the
> first
> > number "4." and release, ACS 13.X, 14.X, 15.X and so on. Every version
> will
> > receive new impressing version number and everyone could be happy about
> > that.
> >
> > Going to version "5" currently looks like as an intention to refresh but
> > with very poor motivation. At least to me.
> >
> > The discussion is strongly welcome.
> >
> >
> >
> > --
> > 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/>
> >
>
>
> --
> Rafael Weingärtner
>


--
Rafael Weingärtner

Re: Why CloudStack 5

[Tutkowski, Mike]

Is 4.12 a decent candidate to be branded 5.0 or might we be waiting for some 
specific set of backwards-incompatible updates?



From: Rafael Weingärtner 
Sent: Wednesday, January 23, 2019 4:58 PM
To: dev
Cc: users
Subject: Re: Why CloudStack 5

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hello Ivan,
Can you provide reasons why not move to a version 5?

To help you, I will provide why I think we should move to 5.0.0 after 4.12.
Therefore, I would expect this 5.0.0 to be an LTS version as well.

1. To begin with, technically, we should already be in version 5 if we
had been following the semantic versioning we say we follow. We broke
compatibility when Midonet plugin was removed in 4.10, and later, also,
when public APIs from the IAM projects were removed. You can discuss if
those features were broken or not, and if they count as a backward
incompatibility. All in all, it is a removal of public APIs;
2. We want to remove the basic network, and with this move, we can
delete a load of complications and replicated code, which causes more
burden than anything else;
3. There are also some other small details in some PRs, where these
issues with backward compatibility are holding our code and structure
improvements. Therefore, a CloudStack 5.0.0 would free us from these
anchors that we keep dragging around;
4. A new database upgrade scheme…. I do not even need to get into this
topic; all DEVs here know what I am talking about;
5. A proper JPA implementation, a real restful API, adopt a standard
rest framework, and other base technological improvements would be awesome,
but I would say that they are far from here now. And they will be always
distant if we keep holding ourselves back.

All in all, to conclude; it is not about the version number and marketing.
At least for me, I could care less about the number. This is about the
community being able to adopt new trends, new technology, new methods, and
understanding that to move on, we need to let somethings go.

On Tue, Jan 22, 2019 at 1:45 AM Ivan Kudryavtsev 
wrote:

> I decided whether to write it several weeks thinking about the stones and
> rotten potatoes, but still decided to do that. Hope it will not raise the
> stress level.
>
> Colleagues and ACS leaders, I would like to initiate the discussion. Why go
> to CS5 rather than stay with 4.XX. Some thoughts are:
>
> 1. According to the versioning guide, the first number stands for radical
> changes like if the community decided to go from current ORM to Hibernate.
> I don't see the capabilities for such changes and there are no intentions
> for the implementation.
>
> 2. I can realize that we 'stuck' with '4.XX' and the marketing can be
> disappointing from that point of view. Then, OK, let's just skip the first
> number "4." and release, ACS 13.X, 14.X, 15.X and so on. Every version will
> receive new impressing version number and everyone could be happy about
> that.
>
> Going to version "5" currently looks like as an intention to refresh but
> with very poor motivation. At least to me.
>
> The discussion is strongly welcome.
>
>
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks LLC
> Cell RU: +7-923-414-1515
> Cell USA: +1-201-257-1512
> WWW: http://bitworks.software/ 
>


--
Rafael Weingärtner

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

I can participate in the call, Rafael. I have updated the Doodle pool.

On 1/11/19, 11:47 AM, "Rafael Weingärtner"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hello CloudStackers,

Happy new year to everybody! I hope that you all enjoyed the festivities
and are rested and ready for this new, challenging and exciting year ;)

As you all know, we are trying to organize the CCC as a joint event with
TDC in Brazil. We have proposed the topics for presentations, and now the
next step is to schedule a meeting with the TDC organizers. We need to
discuss channels to spread the word regarding the conference, talks
selection process, branding (CCC, Apache CloudStack) with the TDC, and so
on. Who would be willing to join me in this call?

They are unavailable in January. Therefore, I am proposing the call to be
in the first week of February. I am starting a pool in Doodle to see if we
can find the best time and date. As pools tend to get cluttered when we
have a lot of options, I am starting with 4 and 5 of February. Beware that
the time is in GMT-02:00 (Brasilia time). Therefore, before selecting one,
it might be a good idea to check the difference between GMT-02:00 and your
timezone.

The link for the Doodle pool is: https://doodle.com/poll/7dpvtiqg67it452m

If you have any other question or suggestion for dates and time, please do
not hesitate to contact me.

Again, thanks for your (the ACS community) time, attention, and effort.

Let’s make CCC-BR 2019 happen!!

On Mon, Dec 24, 2018 at 2:32 PM Tutkowski, Mike 
wrote:

> Yeah, let’s do a call once more people are back from the holidays. Maybe
> the first or second week of January?
>
> 
> From: Rafael Weingärtner 
> Sent: Monday, December 24, 2018 3:47 AM
> To: users; dev
> Subject: Re: CloudStack Collab in Brazil
>
> NetApp Security WARNING: This is an external email. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> It would be great to have your presence :)
> My idea is to have a call after this period of Christmas and New Year’s
> Eve. I will let you guys know when I get the dates and time.
>
> Thanks for your (the ACS community) time, attention, and effort so far.
>
> On Fri, Dec 21, 2018 at 10:04 PM Tim Mackey  wrote:
>
> > Rafael,
> >
> > I can't do a call next week, but the following week I should be able to.
> > The tracks look great. From my side, assuming I can get travel approval,
> > I'll submit on the cloud security track. Regulations are part of my life
> > these days!
> >
> > -tim
> >
> > On Fri, Dec 21, 2018 at 10:19 AM Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > No date has been set yet. Next week I will contact them again, and
> then I
> > > will reach the community here to set a date. Thanks for the 
willingness
> > to
> > > make this happen! Your participation is essential. You guys have great
> > use
> > > cases of ACS.
> > >
> > > On Fri, Dec 21, 2018 at 12:49 PM Ricardo Makino <
> ricardo.n...@gmail.com>
> > > wrote:
> > >
> > > > Hi Rafael,
> > > >
> > > > I am able to join you in the call, when do you expect it happening?
> > > >
> > > > Maybe we can use doodle (https://doodle.com) to check the schedule
> of
> > > all
> > > > involved in the call.
> > > >
> > > > Best Regards,
> > > > --
> > > > Ricardo Makino
> > > >
> > > >
> > > > On Fri, Dec 21, 2018 at 11:23 AM Rafael Weingärtner <
> > > > rafaelweingart...@gmail.com> wrote:
> > > >
> > > > > Hello Folks,
> > > > >
> > > > > I have submitted the tracks. The next step now is to schedule a
> > meeting
> > > > > with the TDC organizers again. However, at this time, I need some
> of
> > > you
> > > > in
> > > > > the call. We will be discussing channels to spread the word
> regarding
> > > the
> > >

Re: Introduction

[Tutkowski, Mike]

Glad to have you continuing to work in the CloudStack Community, Andrija!

FYI: I've worked with Andrija as a customer of SolidFire the past couple years 
(first having met him in Budapest at a CloudStack Collab Conf). He has great 
experience with CloudStack and it's fantastic that he is able to continue 
helping out the Community while working at ShapeBlue. :)

On 1/11/19, 3:49 AM, "Andrija Panic"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi all,

I would like to take this opportunity to (re)introduce myself - some of you 
already know me from mailing list as Andrija Panic from HIAG/Safe Swiss Cloud.

I have moved forward and joined a great team in ShapeBlue as a Cloud 
Architect and looking forward to further endeavors with CloudStack.
FTR - I'm based in Belgrade, Serbia and been playing with CloudStack for 
last 5 years in production.

Cheers,
Andrija Panić

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

Re: Introduction

[Tutkowski, Mike]

Welcome, Abhishek!

On 1/2/19, 3:54 AM, "Abhishek Kumar"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hello all!


This is Abhishek Kumar. I've recently joined ShapeBlue as Software Engineer 
to work on Cloudstack.
Looking forward to learn and contribute in the project and community in a 
meaningful manner.


Regards,


Abhishek Kumar

Software Engineer

ShapeBlue

abhishek.ku...@shapeblue.com

www.shapeblue.com

abhishek.ku...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

apeblue.com/ | twitter: @shapeblue
> > > > >>
> > > > >> Em 19/12/2018 15:55, "Tim Mackey"  escreveu:
> > > > >>
> > > > >> Gabriel,
> > > > >>
> > > > >> I'm happy to help review proposals if required.
> > > > >>
> > > > >> -tim
> > > > >>
> > > > >> On Wed, Dec 19, 2018 at 12:35 PM Gabriel Beims Bräscher <
> > > > >> gabrasc...@gmail.com> wrote:
> > > > >>
> > > > >> > Hi Rafael,
> > > > >> >
> > > > >> > I am available to help, count on me!
> > > > >> > I have one question. Can anyone (one that is not a
> > > PMC/Committer)
> > > > >> help to
> > > > >> > review presentations?
> > > > >> >
> > > > >> > The divisions for the CFP looks good, adding security
> aspects
> > as
> > > > >> Ricardo
> > > > >> > Makino proposed is also interesting.
> > > > >> >
> > > > >> > Regards,
> > > > >> > Gabriel.
> > > > >> >
> > > > >> > Em qua, 19 de dez de 2018 às 11:12, Cristian Latapiat <
> > > > >> latap...@gmail.com>
> > > > >> > escreveu:
> > > > >> >
> > > > >> > > Hi Rafael ,
> > > > >> > >
> > > > >> > > I am, therefore, available to collaborate and to help you
> in
> > > > >> everything
> > > > >> > > that may be necessary.
> > > > >> > >
> > > > >> > > Regards,
> > > > >> > >
> > > > >> > > Cristian
> > > > >> > >
> > > > >> > > Em seg, 17 de dez de 2018 às 18:49, Rafael Weingärtner <
> > > > >> > > rafaelweingart...@gmail.com> escreveu:
> > > > >> > >
> > > > >> > > > Hey guys,
> > > > >> > > >
> > > > >> > > > Have you guys had time to read through this e-mail? Are
> > > there
> > > > >> > volunteers
> > > > >> > > to
> > > > >> > > > help us make CCC happen in Brazil? We need to provide
> them
> > > the
> > > > >> topics
> > > > >> > of
> > > > >> > > > tracks that we will be participating until 21/12/2018.
> > > > >> > > >
> > > > >> > > > On Thu, Dec 13, 2018 at 7:11 PM Rafael Weingärtner <
> > > > >> > > > rafaelweingart...@gmail.com> wrote:
> > > > >> > > >
> > > > >> > > > > Hello CloudStackers,
> > > > >> > > > >
> > > > >> > > > > I had a few meetings with the TDC folks, and we seem
> to
> > be
> > > > >> moving on.
> > > > >> > > > They
> > > > >> > > > > have a slightly different organization than ApacheCon
> > > > though.
> > > > >> > > Therefore,
> > > > >> > > > we
> > > > >> > > > > were asked to provide them with some “track topics”
> that
> > > fit
> > > > >> in the
> > > > >> > > area
> > > > >> > > > of
> > > > >> > > > > Cloud Computing. Then, we could direct presentations
> to
> > > one
> > > > >> of these
> > > > >> > > > > tracks. The idea is that the international tracks (the
> > > ones
> > > > >> that will
> > > > >> > > be
> > > > >> > > > in
> > > > >> > > > > English) will not be parallelized to enable the
> audience
> > > to
> > > > >> attend
> > > > >> > all
> > > > >> > > of
> > > > >> > > > > them (this means, one for each day). Also, the tracks
> > will
> > > > >> receive
> > > > >> > > > > presentations from other people that are not in our
> > > bubble,
> > &g

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

Hi Rafael,

The divisions you listed for the CFP make good sense to me. :)

Unless we have feedback from others here, let’s use what you have. It seems the 
deadline to provide these is coming quickly.

Thanks for all your work here, Rafael!
Mike



From: Rafael Weingärtner 
Sent: Tuesday, December 18, 2018 3:58 AM
To: users
Cc: dev@cloudstack.apache.org
Subject: Re: CloudStack Collab in Brazil

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Awesome, thanks Mike.
As the current VP, your participation is very important :)

Also, what do you think about the topics to address at the conference? Do
you have some suggestions?

On Mon, Dec 17, 2018 at 8:50 PM Tutkowski, Mike 
wrote:

> I can help out with the CFP (looking through and helping to select
> presentations).
>
>
> 
> From: Rafael Weingärtner 
> Sent: Monday, December 17, 2018 1:49 PM
> To: users
> Cc: dev@cloudstack.apache.org
> Subject: Re: CloudStack Collab in Brazil
>
> NetApp Security WARNING: This is an external email. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> Hey guys,
>
> Have you guys had time to read through this e-mail? Are there volunteers to
> help us make CCC happen in Brazil? We need to provide them the topics of
> tracks that we will be participating until 21/12/2018.
>
> On Thu, Dec 13, 2018 at 7:11 PM Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Hello CloudStackers,
> >
> > I had a few meetings with the TDC folks, and we seem to be moving on.
> They
> > have a slightly different organization than ApacheCon though. Therefore,
> we
> > were asked to provide them with some “track topics” that fit in the area
> of
> > Cloud Computing. Then, we could direct presentations to one of these
> > tracks. The idea is that the international tracks (the ones that will be
> in
> > English) will not be parallelized to enable the audience to attend all of
> > them (this means, one for each day). Also, the tracks will receive
> > presentations from other people that are not in our bubble, and this is
> > great (at least I found this awesome), because different people with
> > different backgrounds would come together on the same track, which in
> turn
> > means, people that might not know ACS would have the opportunity not just
> > to meet the solution, but also the people behind it.
> >
> > So, this is what I have in mind:
> >
> > - Cloud computing (area/topic)
> > - cloud orchestration -- this would be the track where topics
> > regarding features, and cloud orchestration systems (e.g. CloudStack)
> > design and structure would be presented
> > - DevOps -- track for presentations that address the day-to-day of
> > CloudStack (or OpenStack) developers and the daily life of operators with
> > tasks such as debugging and troubleshooting
> > - tests -- track for discussing the Q process and testing methods
> > for clouds
> > - cloud open source ecosystem -- track focusing on the cloud
> > ecosystem, where people can address things relating the job market,
> > business opportunities, and the management process of highly
> heterogeneous
> > and distributed communities in OpenSource (such as CloudStack)
> >
> >
> > What do you guys think of these divisions for the CFP?
> > Also, we might need help to review and select presentation proposals.
> > Would some of you guys be willing to help on this process?
> >
> > And last, but not least, it would be awesome if companies linked to ACS
> > are interested to be the sponsors of tracks or the event. They have sent
> me
> > the brochure and sponsorship prospects from 2018 so we can get to know
> > better the conference [1]. The attendance report and prospectus are in
> > English, and for instance, in 2018 the TDC event in Florianopolis (where
> we
> > are proposing to have CCC in 2019) received about 4000 people. The
> > sponsorship prospectus for 2019 events is being prepared, and I guess if
> > there are interested parties on this, you can reach them directly, or if
> > you have some problems to do that, I can help you guys as well.
> >
> > [1]
> >
> https://www.dropbox.com/sh/53ujp2usf402dlj/AAA1a2jZPddGcAT8ZosRiGCAa?dl=0
> >
> > On Wed, Oct 24, 2018 at 8:16 PM Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> > wrote:
> >
> >> Thanks, Rafael!
> >>
> >> The dates work for me.
> >>
>

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

I can help out with the CFP (looking through and helping to select 
presentations).



From: Rafael Weingärtner 
Sent: Monday, December 17, 2018 1:49 PM
To: users
Cc: dev@cloudstack.apache.org
Subject: Re: CloudStack Collab in Brazil

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hey guys,

Have you guys had time to read through this e-mail? Are there volunteers to
help us make CCC happen in Brazil? We need to provide them the topics of
tracks that we will be participating until 21/12/2018.

On Thu, Dec 13, 2018 at 7:11 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Hello CloudStackers,
>
> I had a few meetings with the TDC folks, and we seem to be moving on. They
> have a slightly different organization than ApacheCon though. Therefore, we
> were asked to provide them with some “track topics” that fit in the area of
> Cloud Computing. Then, we could direct presentations to one of these
> tracks. The idea is that the international tracks (the ones that will be in
> English) will not be parallelized to enable the audience to attend all of
> them (this means, one for each day). Also, the tracks will receive
> presentations from other people that are not in our bubble, and this is
> great (at least I found this awesome), because different people with
> different backgrounds would come together on the same track, which in turn
> means, people that might not know ACS would have the opportunity not just
> to meet the solution, but also the people behind it.
>
> So, this is what I have in mind:
>
> - Cloud computing (area/topic)
> - cloud orchestration -- this would be the track where topics
> regarding features, and cloud orchestration systems (e.g. CloudStack)
> design and structure would be presented
> - DevOps -- track for presentations that address the day-to-day of
> CloudStack (or OpenStack) developers and the daily life of operators with
> tasks such as debugging and troubleshooting
> - tests -- track for discussing the Q process and testing methods
> for clouds
> - cloud open source ecosystem -- track focusing on the cloud
> ecosystem, where people can address things relating the job market,
> business opportunities, and the management process of highly heterogeneous
> and distributed communities in OpenSource (such as CloudStack)
>
>
> What do you guys think of these divisions for the CFP?
> Also, we might need help to review and select presentation proposals.
> Would some of you guys be willing to help on this process?
>
> And last, but not least, it would be awesome if companies linked to ACS
> are interested to be the sponsors of tracks or the event. They have sent me
> the brochure and sponsorship prospects from 2018 so we can get to know
> better the conference [1]. The attendance report and prospectus are in
> English, and for instance, in 2018 the TDC event in Florianopolis (where we
> are proposing to have CCC in 2019) received about 4000 people. The
> sponsorship prospectus for 2019 events is being prepared, and I guess if
> there are interested parties on this, you can reach them directly, or if
> you have some problems to do that, I can help you guys as well.
>
> [1]
> https://www.dropbox.com/sh/53ujp2usf402dlj/AAA1a2jZPddGcAT8ZosRiGCAa?dl=0
>
> On Wed, Oct 24, 2018 at 8:16 PM Tutkowski, Mike 
> wrote:
>
>> Thanks, Rafael!
>>
>> The dates work for me.
>>
>> Get Outlook for iOS<https://aka.ms/o0ukef>
>> 
>> From: Rafael Weingärtner 
>> Sent: Wednesday, October 24, 2018 5:02:14 PM
>> To: users
>> Cc: dev
>> Subject: Re: CloudStack Collab in Brazil
>>
>> NetApp Security WARNING: This is an external email. Do not click links or
>> open attachments unless you recognize the sender and know the content is
>> safe.
>>
>>
>>
>>
>> Yes, they already have a date set. It should be 23 - 27 April, 2019.
>> I should be talking with them again this week to check what we need to
>> move
>> thing forward.
>>
>> What do you guys think about these dates?
>>
>> On Mon, Oct 22, 2018 at 5:07 PM Tutkowski, Mike <
>> mike.tutkow...@netapp.com>
>> wrote:
>>
>> > Hi Rafael,
>> >
>> > Do you have a specific date in mind for CCC Brazil? It sounds like, in
>> > general, we are looking at April.
>> >
>> > Thanks!
>> > Mike
>> >
>> > On 10/1/18, 12:51 PM, "Rafael Weingärtner" > >
>> > wrote:
>> >
>> > NetApp Security WARNING: This is an external email. Do not 

Re: new committer: Boris Stoyanov (AKA Bobby)

[Tutkowski, Mike]

Congratulations, Bobby!



From: Paul Angus 
Sent: Thursday, December 13, 2018 2:29 AM
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Cc: Boris Stoyanov
Subject: new committer: Boris Stoyanov (AKA Bobby)

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi Everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Boris Stoyanov to become a committer and we are pleased
to announce that he has accepted.

Please join me in congratulating Bobby!


Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.



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

Videos from September CCC Montreal now live

[Tutkowski, Mike]

Hi everyone,

Just an FYI that the videos from the CloudStack Collaboration Conference that 
took place in Montreal last September are available here: 
https://www.youtube.com/playlist?list=PLW7vgBNPiQhkJOwgkEw1bEc4IGDXnkzs7

Thanks to ShapeBlue for recording the presentations!
Mike

Re: [ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.2.0

[Tutkowski, Mike]

Thanks, Paul and all those who participated in this release!



From: Paul Angus 
Sent: Monday, November 26, 2018 8:05 AM
To: dev@cloudstack.apache.org; market...@cloudstack.apache.org; 
annou...@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: [ANNOUNCE] Apache CloudStack LTS Maintenance Release 4.11.2.0

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Announcing Apache CloudStack LTS Maintenance Release 4.11.2.0

The Apache CloudStack project is pleased to announce the release of CloudStack 
4.11.2.0 as part of its LTS 4.11.x releases. The CloudStack 4.11.2.0 release 
contains more than 70 fixes since the CloudStack 4.11.1.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.2.0 release notes include a full list of issues fixed:
http://docs.cloudstack.apache.org/en/4.11.2.0/releasenotes/index.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.2.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.2.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


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

[ANNOUNCE] New committer: Andrija Panić

[Tutkowski, Mike]

Hi everyone,

The Project Management Committee (PMC) for Apache CloudStack
has invited Andrija Panić to become a committer and I am pleased
to announce that he has accepted.

Please join me in congratulating Andrija on this accomplishment.

Thanks!
Mike

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

+1 (binding)

I performed manual testing of a Basic Zone making use of vSphere and XenServer.

On 11/16/18, 5:49 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




We're looking good so far, but I'd still like some more votes (hopefully 
+1s  ), Please do test and cast your vote.

Thanks.


Kind regards,

Paul Angus

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




-Original Message-
From: Andrija Panic 
Sent: 16 November 2018 12:12
To: dev 
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

+1

Tested:
- KVM environment
- building DEB packages for Ubuntu
- advanced and basic zone deployment, MGMT srv on Ubuntu 14.04, KVM Ubuntu
14.04 (qemu versions equivalent to Ubuntu 16.04)
- a bunch of integration tests done from in-house suite of tests (system 
and user tests)
- online and offline storage migration from NFS/CEPH to SolidFire


On Fri, 16 Nov 2018 at 10:13, Dag Sonstebo 
wrote:

> +1
>
> Various customer related configurations and lifecycle operations, all
> looking good.
>
> Environment:
> - Mgmt: CentOS7.5
> - HV: VMware 5.5
> - Advanced zone
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 16/11/2018, 08:48, "Boris Stoyanov" 
> wrote:
>
> +1
>
> I’ve did an upgrade all the way from 4.6 to rc5 and it was
> successful, I’ve also managed to run some basic lifecycle operation
> and it was looking good.
>
> Regards,
> Bobby.
>
>
> boris.stoya...@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
>
>
>
> > On 15 Nov 2018, at 21:44, Gabriel Beims Bräscher 
> wrote:
> >
> > +1 Deployed local environment and tested VM/host/storage lifecycles.
> >
> > Hosts: KVM running on Ubuntu 16.04
> > Management server and database: running on Ubuntu 16.04
> > - create/use/delete system and user VMs
    >     > - register new template
> > - register service offering
> > - work with hosts (add, maintenance, remove)
> >
> > Em qui, 15 de nov de 2018 às 03:21, Tutkowski, Mike <
> > mike.tutkow...@netapp.com> escreveu:
> >
> >> Thanks, Rohit!
> >>
> >>
> >> 
> >> From: Rohit Yadav 
> >> Sent: Wednesday, November 14, 2018 9:07 PM
> >> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> >> Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5
> >>
> >> NetApp Security WARNING: This is an external email. Do not click
> links or
> >> open attachments unless you recognize the sender and know the
> content is
> >> safe.
> >>
> >>
> >>
> >>
> >> Hi Mike, Paul, everyone,
> >>
> >>
> >> I tested the same on a 4.9.3.1 based VMware 5.5u3 + svs + basic
> zone and
> >> could see the same behaviour. Therefore, it's not a regression but 
a
> >> limitation from the past. Basic zone provides L3 isolation by means
> of
> >> security group (host-level firewall) which is not supported for
> VMware. I
> >> think nobody reported this in the past because nobody uses
> VMware+basic
> >> zone, I've opened an issue for this issue:
> >> https://github.com/apache/cloudstack/issues/3031
> >>
> >>
> >> Let's continue testing and voting for RC5, and let's aim to fix for
> this
> >> limitation in future 4.11.3+, 4.12.0+.
> >>
> >>
> >> - Rohit
>     >>
> >> <https://cloudstack.apache.org>
> >>
> >>
> >>
> >> 

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

Thanks, Rohit!



From: Rohit Yadav 
Sent: Wednesday, November 14, 2018 9:07 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi Mike, Paul, everyone,


I tested the same on a 4.9.3.1 based VMware 5.5u3 + svs + basic zone and could 
see the same behaviour. Therefore, it's not a regression but a limitation from 
the past. Basic zone provides L3 isolation by means of security group 
(host-level firewall) which is not supported for VMware. I think nobody 
reported this in the past because nobody uses VMware+basic zone, I've opened an 
issue for this issue: https://github.com/apache/cloudstack/issues/3031


Let's continue testing and voting for RC5, and let's aim to fix for this 
limitation in future 4.11.3+, 4.12.0+.


- Rohit

<https://cloudstack.apache.org>




From: Tutkowski, Mike 
Sent: Thursday, November 15, 2018 4:24:46 AM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I should note that I’m running vSphere 5.5, by the way. I believe that’s still 
supported in CS 4.11.

On 11/14/18, 3:52 PM, "Tutkowski, Mike"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




The VR doesn’t show as having an IP address.

On 11/14/18, 3:50 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Mgmt. server should ssh into VR.
I'll fire a similar build in out lab.


paul.an...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue




-Original Message-
From: Tutkowski, Mike 
Sent: 14 November 2018 22:41
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

Right, I’ve compiled and run with –Dnoredist. The SSVM and CPVM come up fine. 
They both show the VM and agent running. The VR boots up. I can see it at the 
login prompt in vSphere Client. I don’t see any obvious errors in cloud.log. 
Maybe a port is blocked and it can’t talk to the management server?

On 11/14/18, 3:10 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




I've tested in an ubuntu16 basic zone but not vmware basic zone - I guess that 
it goes without say that you know to use build nonoss from vmware... have you 
used the 6.5 sdk ?
I think that it always says requires upgrade until the VR checks in.
Have the SSVM and CPVM checked in ok? If you go on the VR through the vCenter 
console what do you see?

paul.an...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue




-Original Message-
From: Tutkowski, Mike 
Sent: 14 November 2018 21:16
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I’m having a hard time getting the VR with vSphere to come up successfully.

I built the code from source (the specified commit) and am using the system VM 
template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR in the GUI, 
it says Requires Upgrade is Yes. When I click the button to upgrade the 
template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 16th Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

I should note that I’m running vSphere 5.5, by the way. I believe that’s still 
supported in CS 4.11.

On 11/14/18, 3:52 PM, "Tutkowski, Mike"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




The VR doesn’t show as having an IP address.

On 11/14/18, 3:50 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.




Mgmt. server should ssh into VR.
I'll fire a similar build in out lab.


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




-Original Message-
        From: Tutkowski, Mike 
Sent: 14 November 2018 22:41
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

Right, I’ve compiled and run with –Dnoredist. The SSVM and CPVM come up 
fine. They both show the VM and agent running. The VR boots up. I can see it at 
the login prompt in vSphere Client. I don’t see any obvious errors in 
cloud.log. Maybe a port is blocked and it can’t talk to the management server?

On 11/14/18, 3:10 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.




I've tested in an ubuntu16 basic zone but not vmware basic zone - I 
guess that it goes without say that you know to use build nonoss from vmware... 
have you used the 6.5 sdk ?
I think that it always says requires upgrade until the VR checks in.
Have the SSVM and CPVM checked in ok?  If you go on the VR through 
the vCenter console what do you see?

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




-Original Message-----
    From: Tutkowski, Mike 
Sent: 14 November 2018 21:16
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I’m having a hard time getting the VR with vSphere to come up 
successfully.

I built the code from source (the specified commit) and am using 
the system VM template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR 
in the GUI, it says Requires Upgrade is Yes. When I click the button to upgrade 
the template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 
16th Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue.com/testing/41120rc5/

The release notes are still work-in-progress, but the systemvm 
template upgrade section has been updated.

4.11.2.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41120rc5/

   

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

The VR’s IP address was not being reported on the main GUI window, but I found 
it in the VR details (and also via ifconfig on the VR itself).

I can ping both ways successfully: From the management server to the VR and 
vice versa.

On 11/14/18, 3:52 PM, "Tutkowski, Mike"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




The VR doesn’t show as having an IP address.

On 11/14/18, 3:50 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.




Mgmt. server should ssh into VR.
I'll fire a similar build in out lab.


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




-Original Message-
        From: Tutkowski, Mike 
Sent: 14 November 2018 22:41
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

Right, I’ve compiled and run with –Dnoredist. The SSVM and CPVM come up 
fine. They both show the VM and agent running. The VR boots up. I can see it at 
the login prompt in vSphere Client. I don’t see any obvious errors in 
cloud.log. Maybe a port is blocked and it can’t talk to the management server?

On 11/14/18, 3:10 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.




I've tested in an ubuntu16 basic zone but not vmware basic zone - I 
guess that it goes without say that you know to use build nonoss from vmware... 
have you used the 6.5 sdk ?
I think that it always says requires upgrade until the VR checks in.
Have the SSVM and CPVM checked in ok?  If you go on the VR through 
the vCenter console what do you see?

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




-Original Message-----
    From: Tutkowski, Mike 
Sent: 14 November 2018 21:16
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I’m having a hard time getting the VR with vSphere to come up 
successfully.

I built the code from source (the specified commit) and am using 
the system VM template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR 
in the GUI, it says Requires Upgrade is Yes. When I click the button to upgrade 
the template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 
16th Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue.com/testing/41120rc5/

The release notes are still work-in-progress, but the systemvm 
template upgrade section has been updated.

4.11.2.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41120rc5/

   

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

The VR doesn’t show as having an IP address.

On 11/14/18, 3:50 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Mgmt. server should ssh into VR.
I'll fire a similar build in out lab.


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




-Original Message-
From: Tutkowski, Mike 
Sent: 14 November 2018 22:41
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

Right, I’ve compiled and run with –Dnoredist. The SSVM and CPVM come up 
fine. They both show the VM and agent running. The VR boots up. I can see it at 
the login prompt in vSphere Client. I don’t see any obvious errors in 
cloud.log. Maybe a port is blocked and it can’t talk to the management server?

On 11/14/18, 3:10 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.




I've tested in an ubuntu16 basic zone but not vmware basic zone - I 
guess that it goes without say that you know to use build nonoss from vmware... 
have you used the 6.5 sdk ?
I think that it always says requires upgrade until the VR checks in.
Have the SSVM and CPVM checked in ok?  If you go on the VR through the 
vCenter console what do you see?

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




-Original Message-
        From: Tutkowski, Mike 
Sent: 14 November 2018 21:16
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I’m having a hard time getting the VR with vSphere to come up 
successfully.

I built the code from source (the specified commit) and am using the 
system VM template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR in 
the GUI, it says Requires Upgrade is Yes. When I click the button to upgrade 
the template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 16th 
Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue.com/testing/41120rc5/

The release notes are still work-in-progress, but the systemvm 
template upgrade section has been updated.

4.11.2.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41120rc5/

Only the following changes have been added to RC5:


+-+--+---+--++
| Version | Github   | Type  | Priority | 
Description|

+=+==+===+==++
| 4.11.2.0| `#3018`_ |   |  | 
Prev

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

Right, I’ve compiled and run with –Dnoredist. The SSVM and CPVM come up fine. 
They both show the VM and agent running. The VR boots up. I can see it at the 
login prompt in vSphere Client. I don’t see any obvious errors in cloud.log. 
Maybe a port is blocked and it can’t talk to the management server?

On 11/14/18, 3:10 PM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




I've tested in an ubuntu16 basic zone but not vmware basic zone - I guess 
that it goes without say that you know to use build nonoss from vmware... have 
you used the 6.5 sdk ?
I think that it always says requires upgrade until the VR checks in.
Have the SSVM and CPVM checked in ok?  If you go on the VR through the 
vCenter console what do you see?

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




-Original Message-
From: Tutkowski, Mike 
Sent: 14 November 2018 21:16
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

I’m having a hard time getting the VR with vSphere to come up successfully.

I built the code from source (the specified commit) and am using the system 
VM template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR in the 
GUI, it says Requires Upgrade is Yes. When I click the button to upgrade the 
template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 16th Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue.com/testing/41120rc5/

The release notes are still work-in-progress, but the systemvm template 
upgrade section has been updated.

4.11.2.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41120rc5/

Only the following changes have been added to RC5:


+-+--+---+--++
| Version | Github   | Type  | Priority | 
Description|

+=+==+===+==++
| 4.11.2.0| `#3018`_ |   |  | 
Prevent error on GroupAnswers on VR creation   |

+-+--+---+--++
| 4.11.2.0| `#3007`_ |   |  | Add 
missing ConfigDrive entries on existing zones after|
| |  |   |  | 
upgrade|

+-+--+---+--++
| 4.11.2.0| `#2980`_ |   |  | 
[4.11] Fix set initial reservation on public IP ranges |

+-+--+---+--++
| 4.11.2.0| `#3010`_ |   |  | Fix 
DirectNetworkGuru canHandle checks for lowercase   |
| |  |   |

Re: [VOTE] Apache CloudStack 4.11.2.0 RC5

[Tutkowski, Mike]

I’m having a hard time getting the VR with vSphere to come up successfully.

I built the code from source (the specified commit) and am using the system VM 
template specified in this e-mail chain.

I’m running in a Basic Zone. When I look at the details for the VR in the GUI, 
it says Requires Upgrade is Yes. When I click the button to upgrade the 
template, the operation fails.

Thoughts?

On 11/13/18, 6:59 AM, "Paul Angus"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hi All,

I've created a 4.11.2.0 release (RC5), 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.2.0-RC20181113T0924
Commit: 5aae410dfce2bef5cc21a0892370cb5d0628f681

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

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

The vote will be open for 72 hours - until 14:00 GMT on Friday 16th Nov.

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 
5aae410dfce2bef5cc21a0892370cb5d0628f681 and published RC5 repository here:
http://packages.shapeblue.com/testing/41120rc5/

The release notes are still work-in-progress, but the systemvm template 
upgrade section has been updated.

4.11.2.0 systemvm templates are available from here:
http://packages.shapeblue.com/testing/systemvm/41120rc5/

Only the following changes have been added to RC5:


+-+--+---+--++
| Version | Github   | Type  | Priority | 
Description|

+=+==+===+==++
| 4.11.2.0| `#3018`_ |   |  | Prevent 
error on GroupAnswers on VR creation   |

+-+--+---+--++
| 4.11.2.0| `#3007`_ |   |  | Add 
missing ConfigDrive entries on existing zones after|
| |  |   |  | upgrade   
 |

+-+--+---+--++
| 4.11.2.0| `#2980`_ |   |  | [4.11] 
Fix set initial reservation on public IP ranges |

+-+--+---+--++
| 4.11.2.0| `#3010`_ |   |  | Fix 
DirectNetworkGuru canHandle checks for lowercase   |
| |  |   |  | isolation 
methods  |

+-+--+---+--++

.. _`#3012`: https://github.com/apache/cloudstack/pull/3012
.. _`#3018`: https://github.com/apache/cloudstack/pull/3018
.. _`#3007`: https://github.com/apache/cloudstack/pull/3007
.. _`#2980`: https://github.com/apache/cloudstack/pull/2980
.. _`#3010`: https://github.com/apache/cloudstack/pull/3010



Kind regards,

Paul Angus


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

Re: Exception in MS on master

[Tutkowski, Mike]

Thanks, Rohit!

I must have sent this e-mail while I was in Montréal at CCC. I had forgotten 
that I sent this out. :)


From: Rohit Yadav 
Sent: Sunday, November 11, 2018 11:26:38 PM
To: dev@cloudstack.apache.org
Subject: Re: Exception in MS on master

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi Mike,


I came across this as well, looks like a regression on master. I've opened a 
bug: https://github.com/apache/cloudstack/issues/2935


- Rohit

<https://cloudstack.apache.org>




From: Tutkowski, Mike 
Sent: Wednesday, September 26, 2018 1:58:51 AM
To: dev@cloudstack.apache.org
Subject: Exception in MS on master

Hi everyone,

I was building a new cloud and came across the following exception when running 
the management server (below).

Any thoughts on what this is about?

Thanks!
Mike

WARN  [o.a.c.e.o.NetworkOrchestrator] (Network-Scavenger-1:ctx-8cd291c0) 
(logid:4f70c744) Caught exception while running network gc:
com.cloud.utils.exception.CloudRuntimeException: Caught: 
com.mysql.jdbc.JDBC4PreparedStatement@6ffe01cc: SELECT networks.id FROM 
networks  INNER JOIN network_offerings ON 
networks.network_offering_id=network_offerings.id  INNER JOIN op_networks ON 
networks.id=op_networks.id WHERE networks.removed IS NULL  AND  
(op_networks.nics_count = ** NOT SPECIFIED **  AND op_networks.gc = ** NOT 
SPECIFIED **  AND op_networks.check_for_gc = ** NOT SPECIFIED ** )
at 
com.cloud.utils.db.GenericDaoBase.customSearchIncludingRemoved(GenericDaoBase.java:507)
at com.cloud.utils.db.GenericDaoBase.customSearch(GenericDaoBase.java:518)
at 
com.cloud.network.dao.NetworkDaoImpl.findNetworksToGarbageCollect(NetworkDaoImpl.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:338)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:197)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy96.findNetworksToGarbageCollect(Unknown Source)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2761)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2745)
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 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
com.cloud.utils.db.GenericDaoBase.prepareAttribute(GenericDaoBase.java:1519)
at 
com.cloud.utils.db.GenericDaoBase.addJoinAttributes(GenericDaoBase.java:774)
at 
com.cloud.utils.db.GenericDaoBase.customSearchIncludingRemoved(GenericDaoBase.java:476)
... 29 more


rohit.ya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, 

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

Thanks, Rafael!

The dates work for me.

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Rafael Weingärtner 
Sent: Wednesday, October 24, 2018 5:02:14 PM
To: users
Cc: dev
Subject: Re: CloudStack Collab in Brazil

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Yes, they already have a date set. It should be 23 -  27 April, 2019.
I should be talking with them again this week to check what we need to move
thing forward.

What do you guys think about these dates?

On Mon, Oct 22, 2018 at 5:07 PM Tutkowski, Mike 
wrote:

> Hi Rafael,
>
> Do you have a specific date in mind for CCC Brazil? It sounds like, in
> general, we are looking at April.
>
> Thanks!
> Mike
>
> On 10/1/18, 12:51 PM, "Rafael Weingärtner" 
> wrote:
>
> NetApp Security WARNING: This is an external email. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> Yes, that is what I also believe. From the feedback, I think we can
> easily
> use 10 presentations. I will move on with the organization. I think it
> is
> feasible to get more room space in case we receive more presentation
> and
> people. I will try to not overlap presentations though (like we did in
> ApacheCon).
>
> On Mon, Oct 1, 2018 at 3:36 PM Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> wrote:
>
> > I guess it depends on how many people expect to be able to attend.
> >
> > Ten presentation slots is probably a good starting point.
> >
> > Get Outlook for iOS<https://aka.ms/o0ukef>
> > 
> > From: Rafael Weingärtner 
> > Sent: Monday, October 1, 2018 10:10:55 AM
> > To: users
> > Cc: dev
> > Subject: Re: CloudStack Collab in Brazil
> >
> > NetApp Security WARNING: This is an external email. Do not click
> links or
> > open attachments unless you recognize the sender and know the
> content is
> > safe.
> >
> >
> >
> >
> > Thank you guys for the feedback!
> >
> > I will reach out the organizers to discuss our requirements. What do
> you
> > guys think that we need?
> > Would 10 presentation slots (50min. each) be enough? Or, do you guys
> think
> > that we need more?
> >
> > Also, I think that we should also do a Hackathon. Therefore, I will
> also be
> > asking for a room such as the one we used in Montreal.
> >
> > On Mon, Oct 1, 2018 at 12:03 PM Nicolas Vazquez <
> > nicolas.vazq...@shapeblue.com> wrote:
> >
> > > I would be interested in an event in Brazil as well.
> > >
> > >
> > > Regards,
> > >
> > > Nicolas Vazquez
> > >
> > > ________
> > > From: Gabriel Beims Bräscher 
> > > Sent: Monday, October 1, 2018 11:58:07 AM
> > > To: users
> > > Cc: dev
> > > Subject: Re: CloudStack Collab in Brazil
> > >
> > > As a Brazilian, that lives in Florianópolis, I cannot pass this
> > opportunity
> > > ;)
> > > Count on me!
> > >
> > > Em seg, 1 de out de 2018 às 11:27, Tutkowski, Mike <
> > > mike.tutkow...@netapp.com> escreveu:
> > >
> > > > I would be really interested in an event in Brazil.
> > > >
> > > > 
> > > > From: Rafael Weingärtner 
> > > > Sent: Monday, October 1, 2018 5:38 AM
> > > > To: users
> > > > Cc: dev
> > > > Subject: Re: CloudStack Collab in Brazil
> > > >
> > > > NetApp Security WARNING: This is an external email. Do not click
> links
> > or
> > > > open attachments unless you recognize the sender and know the
> content
> > is
> > > > safe.
> > > >
> > > >
> > > >
> > > >
> > > > Hey Marco,
> > > > Yes, they run a very successful conference every year. I have
> just got
> > > back
> > > > from Montreal, and I talked with people there regarding the
> conference.
> > > >
> > > > Now, for all CloudStackers (users and devs); I will repe

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

Hi Rafael,

Do you have a specific date in mind for CCC Brazil? It sounds like, in general, 
we are looking at April.

Thanks!
Mike

On 10/1/18, 12:51 PM, "Rafael Weingärtner"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Yes, that is what I also believe. From the feedback, I think we can easily
use 10 presentations. I will move on with the organization. I think it is
feasible to get more room space in case we receive more presentation and
people. I will try to not overlap presentations though (like we did in
ApacheCon).

On Mon, Oct 1, 2018 at 3:36 PM Tutkowski, Mike 
wrote:

> I guess it depends on how many people expect to be able to attend.
>
> Ten presentation slots is probably a good starting point.
>
> Get Outlook for iOS<https://aka.ms/o0ukef>
> 
> From: Rafael Weingärtner 
> Sent: Monday, October 1, 2018 10:10:55 AM
> To: users
> Cc: dev
> Subject: Re: CloudStack Collab in Brazil
>
> NetApp Security WARNING: This is an external email. Do not click links or
> open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> Thank you guys for the feedback!
>
> I will reach out the organizers to discuss our requirements. What do you
> guys think that we need?
> Would 10 presentation slots (50min. each) be enough? Or, do you guys think
> that we need more?
>
> Also, I think that we should also do a Hackathon. Therefore, I will also 
be
> asking for a room such as the one we used in Montreal.
>
> On Mon, Oct 1, 2018 at 12:03 PM Nicolas Vazquez <
> nicolas.vazq...@shapeblue.com> wrote:
>
> > I would be interested in an event in Brazil as well.
> >
> >
> > Regards,
> >
> > Nicolas Vazquez
> >
> > 
> > From: Gabriel Beims Bräscher 
> > Sent: Monday, October 1, 2018 11:58:07 AM
> > To: users
> > Cc: dev
> > Subject: Re: CloudStack Collab in Brazil
> >
> > As a Brazilian, that lives in Florianópolis, I cannot pass this
> opportunity
> > ;)
> > Count on me!
> >
> > Em seg, 1 de out de 2018 às 11:27, Tutkowski, Mike <
> > mike.tutkow...@netapp.com> escreveu:
> >
> > > I would be really interested in an event in Brazil.
> > >
> > > 
> > > From: Rafael Weingärtner 
> > > Sent: Monday, October 1, 2018 5:38 AM
> > > To: users
> > > Cc: dev
> > > Subject: Re: CloudStack Collab in Brazil
> > >
> > > NetApp Security WARNING: This is an external email. Do not click links
> or
> > > open attachments unless you recognize the sender and know the content
> is
> > > safe.
> > >
> > >
> > >
> > >
> > > Hey Marco,
> > > Yes, they run a very successful conference every year. I have just got
> > back
> > > from Montreal, and I talked with people there regarding the 
conference.
> > >
> > > Now, for all CloudStackers (users and devs); I will repeat what I said
> in
> > > Montreal. The TDC conference will happen with or without us. 
Therefore,
> > we
> > > only need to decide if we will join them in their Cloud tracks. We did
> > not
> > > hear much feedback here, but I will try again.
> > >
> > > If you are part of the CloudStack community (as a contributor,
> committer,
> > > user, operator, and so on), please do provide your feedback. Would you
> > like
> > > to see a CloudStack Collab Conference in Florianopolis, Brazil, 2019? 
I
> > am
> > > only asking you guys, what you think. I do understand the logistics
> > > problems for some folks to attend a conference this far.
> > >
> > > Now, about the city; the island has an airport (airport code = FLN).
> > > However, most flights to FLN will have a connection either on GRU (Sao
> > > Paulo airport) or GIG (Rio de Janeiro airport); KLM, AA, Delta,
> > AirFrance,
> > > Tap, and others have flights to FLN. I have also found some useful
> links
> > in
> > >

Re: Introductions

[Tutkowski, Mike]

Welcome to the CloudStack Community, Anurag! I’m Mike Tutkowski. I work at 
NetApp SolidFire, have been in the CloudStack Community about six years now, 
and currently am serving as the Chair of the CloudStack PMC (Project Management 
Committee).

On 10/14/18, 11:29 PM, "Anurag Awasthi"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Hello Everyone!

It is with great pleasure that I would like to introduce myself to this 
community. I am Anurag and have recently joined ShapeBlue to work on 
CloudStack. Formerly, I have worked at companies like Microsoft and Twitter, 
and I am really looking forward to future collaborations and learnings from all 
of you.

Thank you,
Best Regards,
Anurag Awasthi



anurag.awas...@shapeblue.com
www.shapeblue.com
,
@shapeblue

Re: Marketing page update

[Tutkowski, Mike]

Thanks, Rafael!

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Rafael Weingärtner 
Sent: Wednesday, October 10, 2018 12:58:27 PM
To: dev
Subject: Re: Marketing page update

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Done

On Wed, Oct 10, 2018 at 3:23 PM Tutkowski, Mike 
wrote:

> I kind of like the idea of a redirect.
>
> On 10/10/18, 12:20 PM, "Rafael Weingärtner" 
> wrote:
>
> NetApp Security WARNING: This is an external email. Do not click links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
>
>
>
> Can I delete the wiki users page then? Or, should I replace it with a
> redirect to the cloustack's website?
>
> On Wed, Oct 10, 2018 at 3:14 PM Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> wrote:
>
> > It definitely seems like it would be best to just have this
> information in
> > one place so we don’t have to update two places whenever a change is
> needed.
> >
> > On 10/10/18, 12:10 PM, "Rafael Weingärtner" <
> rafaelweingart...@gmail.com>
> > wrote:
> >
> > NetApp Security WARNING: This is an external email. Do not click
> links
> > or open attachments unless you recognize the sender and know the
> content is
> > safe.
> >
> >
> >
> >
> > What if we remove the wiki page of users? I think it makes more
> sense
> > to
> > use only the one from cloudstack.apache.org.
> >
> > On Wed, Oct 10, 2018 at 3:07 PM Andrija Panic <
> andrija.pa...@gmail.com
> > >
> > wrote:
> >
> > > Perhaps I'm wrong but
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30744222
> > > has a VERY short,brief list of "users" while
> > > https://cloudstack.apache.org/users.html (and
> > >
> >
> https://www.shapeblue.com/are-these-people-really-all-using-cloudstack/ )
> > > -
> > > so I assume its out of date or something
> > >
> > > Anyway, to do (if you like :) );
> > > - remove "Anolim",
> > > - make sure HIAG Data AG 
> (www.hiagdata.com<http://www.hiagdata.com>) is present
> > > - leave Safe Swiss Cloud if already listed (I cant speak for
> them,
> > since
> > > initially they stopped being ACS users/owners, but because of
> > ownership
> > > changes etc etc, might again be engaged with ACS - so can't
> speak
> > for them)
> > >
> > > Thx Rafael
> > >
> > > On Wed, 10 Oct 2018 at 19:54, Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > Then, I can update the wiki for you.
> > > >
> > > > What do you mean by original page outdated?
> > > >
> > > > On Wed, Oct 10, 2018 at 2:51 PM Andrija Panic <
> > andrija.pa...@gmail.com>
> > > > wrote:
> > > >
> > > > > Done PR: https://github.com/apache/cloudstack-www/pull/47
> > > > >
> > > > > As for original page (it seems out of date ???) - I do not
> have
> > WIKI
> > > > > access...
> > > > >
> > > > > Thx
> > > > >
> > > > > On Wed, 10 Oct 2018 at 19:42, Rafael Weingärtner <
> > > > > rafaelweingart...@gmail.com> wrote:
> > > > >
> > > > > > The source code of the second link is managed here:
> > > > > > https://github.com/apache/cloudstack-www
> > > > > > You can even open a PR yourself to fix that.
> > > > > >
> > > > > > The first one, you need wiki write access. I guess, I
> can give
> > it to
> > > > you.
> > > > > > What is your wiki user name?
> > > > > >
> > > > > > On Wed, Oct 10, 2018 at 1:23 PM Andrija Panic <
> > > andrija.pa...@gmail.com
> > > >

Re: Marketing page update

[Tutkowski, Mike]

I kind of like the idea of a redirect.

On 10/10/18, 12:20 PM, "Rafael Weingärtner"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




Can I delete the wiki users page then? Or, should I replace it with a
redirect to the cloustack's website?

On Wed, Oct 10, 2018 at 3:14 PM Tutkowski, Mike 
wrote:

> It definitely seems like it would be best to just have this information in
> one place so we don’t have to update two places whenever a change is 
needed.
>
> On 10/10/18, 12:10 PM, "Rafael Weingärtner" 
> wrote:
>
> NetApp Security WARNING: This is an external email. Do not click links
> or open attachments unless you recognize the sender and know the content 
is
> safe.
>
>
>
>
> What if we remove the wiki page of users? I think it makes more sense
> to
> use only the one from cloudstack.apache.org.
>
> On Wed, Oct 10, 2018 at 3:07 PM Andrija Panic  >
> wrote:
>
> > Perhaps I'm wrong but
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30744222
> > has a VERY short,brief list of "users" while
> > https://cloudstack.apache.org/users.html (and
> >
> https://www.shapeblue.com/are-these-people-really-all-using-cloudstack/ )
> > -
> > so I assume its out of date or something
> >
> > Anyway, to do (if you like :) );
> > - remove "Anolim",
> > - make sure HIAG Data AG (www.hiagdata.com) is present
> > - leave Safe Swiss Cloud if already listed (I cant speak for them,
> since
> > initially they stopped being ACS users/owners, but because of
> ownership
> > changes etc etc, might again be engaged with ACS - so can't speak
> for them)
> >
> > Thx Rafael
> >
> > On Wed, 10 Oct 2018 at 19:54, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Then, I can update the wiki for you.
> > >
> > > What do you mean by original page outdated?
> > >
> > > On Wed, Oct 10, 2018 at 2:51 PM Andrija Panic <
> andrija.pa...@gmail.com>
> > > wrote:
> > >
> > > > Done PR: https://github.com/apache/cloudstack-www/pull/47
> > > >
> > > > As for original page (it seems out of date ???) - I do not have
> WIKI
> > > > access...
> > > >
> > > > Thx
> > > >
> > > > On Wed, 10 Oct 2018 at 19:42, Rafael Weingärtner <
> > > > rafaelweingart...@gmail.com> wrote:
> > > >
> > > > > The source code of the second link is managed here:
> > > > > https://github.com/apache/cloudstack-www
> > > > > You can even open a PR yourself to fix that.
> > > > >
> > > > > The first one, you need wiki write access. I guess, I can give
> it to
> > > you.
> > > > > What is your wiki user name?
> > > > >
> > > > > On Wed, Oct 10, 2018 at 1:23 PM Andrija Panic <
> > andrija.pa...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Actually, I see there is new page
> > > > > > https://cloudstack.apache.org/users.html
> > > > > >
> > > > > > Here please remove Anolim, since this company has been
> RENAMED (3
> > > years
> > > > > > ago) to Safe Swiss Cloud (it's also present on this page).
> > > > > >
> > > > > > I have done Survey, to add HIAG Data AG also to the list.
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > On Wed, 10 Oct 2018 at 18:03, Andrija Panic <
> > andrija.pa...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > 

Re: Marketing page update

[Tutkowski, Mike]

It definitely seems like it would be best to just have this information in one 
place so we don’t have to update two places whenever a change is needed.

On 10/10/18, 12:10 PM, "Rafael Weingärtner"  wrote:

NetApp Security WARNING: This is an external email. Do not click links or 
open attachments unless you recognize the sender and know the content is safe.




What if we remove the wiki page of users? I think it makes more sense to
use only the one from cloudstack.apache.org.

On Wed, Oct 10, 2018 at 3:07 PM Andrija Panic 
wrote:

> Perhaps I'm wrong but
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30744222
> has a VERY short,brief list of "users" while
> https://cloudstack.apache.org/users.html (and
> https://www.shapeblue.com/are-these-people-really-all-using-cloudstack/ )
> -
> so I assume its out of date or something
>
> Anyway, to do (if you like :) );
> - remove "Anolim",
> - make sure HIAG Data AG (www.hiagdata.com) is present
> - leave Safe Swiss Cloud if already listed (I cant speak for them, since
> initially they stopped being ACS users/owners, but because of ownership
> changes etc etc, might again be engaged with ACS - so can't speak for 
them)
>
> Thx Rafael
>
> On Wed, 10 Oct 2018 at 19:54, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Then, I can update the wiki for you.
> >
> > What do you mean by original page outdated?
> >
> > On Wed, Oct 10, 2018 at 2:51 PM Andrija Panic 
> > wrote:
> >
> > > Done PR: https://github.com/apache/cloudstack-www/pull/47
> > >
> > > As for original page (it seems out of date ???) - I do not have WIKI
> > > access...
> > >
> > > Thx
> > >
> > > On Wed, 10 Oct 2018 at 19:42, Rafael Weingärtner <
> > > rafaelweingart...@gmail.com> wrote:
> > >
> > > > The source code of the second link is managed here:
> > > > https://github.com/apache/cloudstack-www
> > > > You can even open a PR yourself to fix that.
> > > >
> > > > The first one, you need wiki write access. I guess, I can give it to
> > you.
> > > > What is your wiki user name?
> > > >
> > > > On Wed, Oct 10, 2018 at 1:23 PM Andrija Panic <
> andrija.pa...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Actually, I see there is new page
> > > > > https://cloudstack.apache.org/users.html
> > > > >
> > > > > Here please remove Anolim, since this company has been RENAMED (3
> > years
> > > > > ago) to Safe Swiss Cloud (it's also present on this page).
> > > > >
> > > > > I have done Survey, to add HIAG Data AG also to the list.
> > > > >
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Wed, 10 Oct 2018 at 18:03, Andrija Panic <
> andrija.pa...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30744222
> > > > > > ("Who uses CloudStack")
> > > > > >
> > > > > > lists "Anolim", which is former name for my company where I
> worked
> > > and
> > > > > > there have been different company changes (company changed name 
a
> > few
> > > > > years
> > > > > > ago...), and that doman doesn't exist any more..
> > > > > >
> > > > > > If someone can update it to "HIAG Data" that would be great. (
> > > > > > www.hiagdata.com)
> > > > > >
> > > > > > Cheers
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Andrija Panić
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Andrija Panić
> > > > >
> > > >
> > > >
> > > > --
> > > > Rafael Weingärtner
> > > >
> > >
> > >
> > > --
> > >
> > > Andrija Panić
> > >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
> --
>
> Andrija Panić
>


--
Rafael Weingärtner

Re: Ansible 2.7: CloudStack related changes and future

[Tutkowski, Mike]

Thanks, Rene, for all of the work you’ve done!

On 10/8/18, 10:02 AM, "Giles Sirett"  wrote:


Rene
Really sorry to hear that. I want to say a massive thank you for all of 
your work with the ansible/cloudstack modules.  I know lots of people have 
benefitted from the modules, a testament to some very cool work

Thank you and good luck with whatever's next for you

Kind regards
Giles

giles.sir...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue




-Original Message-
From: Rene Moser 
Sent: 08 October 2018 12:43
To: us...@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: Ansible 2.7: CloudStack related changes and future

Hi all

First, please note I am leaving my current job by the end of November and I 
don't see that CloudStack will play any role in my professional future.

As a result, I official announce the end of my maintenance for the Ansible 
CloudStack modules with the release of Ansible v2.8.0 in spring 2019.

If anyone is interested to take over, please let me know so I can 
officially introduce him/her to the Ansible community.

Thanks for all the support and joy I have had with CloudStack and the 
community!

Ansible v2.7.0 is released with the following, CloudStack related changes:

David Passante (1):
  cloudstack: new module cs_disk_offering (#41795)

Rene Moser (4):
  cs_firewall: fix idempotence and tests for cloudstack v4.11 (#42458)
  cs_vpc: fix disabled or wrong vpc offering taken (#42465)
  cs_pod: workaround for 4.11 API break (#43944)
  cs_template: implement update and revamp (#37015)

Yoan Blanc (1):
  cs instance root_disk size update resizes the root volume (#43817)

nishiokay (2):
  [cloudstack] fix cs_host example (#42419)
  Update cs_storage_pool.py (#42454)


Best wishes
René

Re: Montréal Hackathon

[Tutkowski, Mike]

Thanks, Simon!

Is anyone able to help Simon with this Jenkins issue?


From: Simon Weller 
Sent: Monday, October 1, 2018 7:52 PM
To: dev@cloudstack.apache.org
Subject: Re: Montréal Hackathon

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Mike,


I've got a PR in for the KVM HyperV Enlightenment feature against master. It 
looks like Jenkins is broken right now, so might need someone to kick it.


- Si


From: Tutkowski, Mike 
Sent: Monday, October 1, 2018 1:28 PM
To: dev@cloudstack.apache.org
Subject: Montréal Hackathon

Hi everyone,

I wanted to send out an e-mail about the hackathon that we held in Montréal 
this past Wednesday (after the two days of the CloudStack Collaboration 
Conference that took place on Monday and Tuesday).

We spent the first 1.5 hours discussing issues we’d like to see addressed 
and/or new features we might be considering. I’ve provided the current list at 
the bottom of this message.

In particular, one item of note is that people seemed interested in quarterly 
remote meetups. The intent of such meetups would be to sync with each other on 
what we’re working on so as to not duplicate effort. We may also have people 
present a bit about a recent feature or item of interest (similar to what we do 
at conferences). In addition, these meetups could provide a nice checkpoint to 
see how we are doing with regards to the items listed below.

Please take a moment, scan through the list, ask questions, and/or send out 
additional areas that you feel the CloudStack Community should be focusing on.

If you were present at the hackathon, feel free to update us on what progress 
you might have made at the hackathon with regards to any topic below.

Thanks!
Mike

Hyper-V enlightenment

Version 5.x of CloudStack

KVM IO bursting

Live VM Migration

RPC Standard interface to VR

Getting INFO easily out of the SSVM

Deprecate old code (OVM?)

CloudMonkey testing

NoVNC in CPVM

CentOS SIG + packaging

VR Programming Optimization

New UI working with API Discovery

Network Models refactoring + designer UI

Marketing Plan

Video series for CloudStack (ex. developers series, users series)

Use GitHub to document aspects of CloudStack (how to build an environment, how 
to start writing code for it, etc.)

Figure out a process for how we'd like issues to be opened, assigned, closed, 
and resolved (using JIRA and GitHub Issues)

Create a true REST API (it can use the existing API behind the scenes).

Logic to generate code in particular use cases so you can focus mainly on your 
business logic.

Use standard libraries that implement JPA, HTTP, etc.

Remote Meetups every quarter

Support IPv6

Re: Montréal Hackathon

[Tutkowski, Mike]

Yes, they are in Trello and thanks to Bobby for putting them there. :)

From: Boris Stoyanov 
Sent: Tuesday, October 2, 2018 12:59:13 AM
To: dev@cloudstack.apache.org
Subject: Re: Montréal Hackathon

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hi guys,

I think we’ve got most of those in Trello, here’s a link 
https://trello.com/invite/b/ztgaumtx/fd51a88ce97b2de02201ed52e99384b9/cloudstack-hackathon-18

Maybe having those ideas there would be easier to manage, + people can comment, 
add details etc to each individually.

Bobby.


boris.stoya...@shapeblue.com
www.shapeblue.com<http://www.shapeblue.com>
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue



On 2 Oct 2018, at 4:51, Simon Weller 
mailto:swel...@ena.com.INVALID>> wrote:

Mike,


I've got a PR in for the KVM HyperV Enlightenment feature against master. It 
looks like Jenkins is broken right now,  so might need someone to kick it.


- Si

____
From: Tutkowski, Mike 
mailto:mike.tutkow...@netapp.com>>
Sent: Monday, October 1, 2018 1:28 PM
To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
Subject: Montréal Hackathon

Hi everyone,

I wanted to send out an e-mail about the hackathon that we held in Montréal 
this past Wednesday (after the two days of the CloudStack Collaboration 
Conference that took place on Monday and Tuesday).

We spent the first 1.5 hours discussing issues we’d like to see addressed 
and/or new features we might be considering. I’ve provided the current list at 
the bottom of this message.

In particular, one item of note is that people seemed interested in quarterly 
remote meetups. The intent of such meetups would be to sync with each other on 
what we’re working on so as to not duplicate effort. We may also have people 
present a bit about a recent feature or item of interest (similar to what we do 
at conferences). In addition, these meetups could provide a nice checkpoint to 
see how we are doing with regards to the items listed below.

Please take a moment, scan through the list, ask questions, and/or send out 
additional areas that you feel the CloudStack Community should be focusing on.

If you were present at the hackathon, feel free to update us on what progress 
you might have made at the hackathon with regards to any topic below.

Thanks!
Mike

Hyper-V enlightenment

Version 5.x of CloudStack

KVM IO bursting

Live VM Migration

RPC Standard interface to VR

Getting INFO easily out of the SSVM

Deprecate old code (OVM?)

CloudMonkey testing

NoVNC in CPVM

CentOS SIG + packaging

VR Programming Optimization

New UI working with API Discovery

Network Models refactoring + designer UI

Marketing Plan

Video series for CloudStack (ex. developers series, users series)

Use GitHub to document aspects of CloudStack (how to build an environment, how 
to start writing code for it, etc.)

Figure out a process for how we'd like issues to be opened, assigned, closed, 
and resolved (using JIRA and GitHub Issues)

Create a true REST API (it can use the existing API behind the scenes).

Logic to generate code in particular use cases so you can focus mainly on your 
business logic.

Use standard libraries that implement JPA, HTTP, etc.

Remote Meetups every quarter

Support IPv6

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

I guess it depends on how many people expect to be able to attend.

Ten presentation slots is probably a good starting point.

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Rafael Weingärtner 
Sent: Monday, October 1, 2018 10:10:55 AM
To: users
Cc: dev
Subject: Re: CloudStack Collab in Brazil

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Thank you guys for the feedback!

I will reach out the organizers to discuss our requirements. What do you
guys think that we need?
Would 10 presentation slots (50min. each) be enough? Or, do you guys think
that we need more?

Also, I think that we should also do a Hackathon. Therefore, I will also be
asking for a room such as the one we used in Montreal.

On Mon, Oct 1, 2018 at 12:03 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:

> I would be interested in an event in Brazil as well.
>
>
> Regards,
>
> Nicolas Vazquez
>
> 
> From: Gabriel Beims Bräscher 
> Sent: Monday, October 1, 2018 11:58:07 AM
> To: users
> Cc: dev
> Subject: Re: CloudStack Collab in Brazil
>
> As a Brazilian, that lives in Florianópolis, I cannot pass this opportunity
> ;)
> Count on me!
>
> Em seg, 1 de out de 2018 às 11:27, Tutkowski, Mike <
> mike.tutkow...@netapp.com> escreveu:
>
> > I would be really interested in an event in Brazil.
> >
> > 
> > From: Rafael Weingärtner 
> > Sent: Monday, October 1, 2018 5:38 AM
> > To: users
> > Cc: dev
> > Subject: Re: CloudStack Collab in Brazil
> >
> > NetApp Security WARNING: This is an external email. Do not click links or
> > open attachments unless you recognize the sender and know the content is
> > safe.
> >
> >
> >
> >
> > Hey Marco,
> > Yes, they run a very successful conference every year. I have just got
> back
> > from Montreal, and I talked with people there regarding the conference.
> >
> > Now, for all CloudStackers (users and devs); I will repeat what I said in
> > Montreal. The TDC conference will happen with or without us. Therefore,
> we
> > only need to decide if we will join them in their Cloud tracks. We did
> not
> > hear much feedback here, but I will try again.
> >
> > If you are part of the CloudStack community (as a contributor, committer,
> > user, operator, and so on), please do provide your feedback. Would you
> like
> > to see a CloudStack Collab Conference in Florianopolis, Brazil, 2019? I
> am
> > only asking you guys, what you think. I do understand the logistics
> > problems for some folks to attend a conference this far.
> >
> > Now, about the city; the island has an airport (airport code = FLN).
> > However, most flights to FLN will have a connection either on GRU (Sao
> > Paulo airport) or GIG (Rio de Janeiro airport); KLM, AA, Delta,
> AirFrance,
> > Tap, and others have flights to FLN. I have also found some useful links
> in
> > English that can be used by your guys to check the city. In this link [1]
> > you can information not only about the city, but the State as well; there
> > are pages in different languages such as English, Spanish, and German (to
> > change the language there is a button in the top-right corner). On these
> > other links [2-3], you can find a guide (English only) of the city; it
> > contains a brief overview and some details about Museums, Beaches, events
> > and so on.
> >
> > I would also be happy to answer any other question that you might have.
> >
> > [1] http://turismo.sc.gov.br/en/cidade/florianopolis/#
> > [2] https://www.floripa-guide.com/attractions/about-florianopolis.html
> > [3] http://www.vivendofloripa.com.br/en/home/
> >
> > On Tue, Sep 25, 2018 at 5:42 PM Marco Sinhoreli <
> > marco.sinhor...@shapeblue.com> wrote:
> >
> > > Hello Rafael,
> > >
> > > I know this conference, last year in TDC Porto Alegre I spoke about ACS
> > > and ansible.
> > >
> > > I was very impressed with them event support and organization, they
> have
> > a
> > > nice approach involving community in the organization. They also have a
> > > good penetration to prospect sponsors.
> > >
> > > I am able to help you in this subject since I am in Brazil as well.
> > >
> > > Best regards,
> > >
> > > Marco Sinhoreli
> > > marco.sinhor...@shapeblue.com
> > > mobile: +55 21 98276 3636
> > >
> > > Av. Brigad

Montréal Hackathon

[Tutkowski, Mike]

Hi everyone,

I wanted to send out an e-mail about the hackathon that we held in Montréal 
this past Wednesday (after the two days of the CloudStack Collaboration 
Conference that took place on Monday and Tuesday).

We spent the first 1.5 hours discussing issues we’d like to see addressed 
and/or new features we might be considering. I’ve provided the current list at 
the bottom of this message.

In particular, one item of note is that people seemed interested in quarterly 
remote meetups. The intent of such meetups would be to sync with each other on 
what we’re working on so as to not duplicate effort. We may also have people 
present a bit about a recent feature or item of interest (similar to what we do 
at conferences). In addition, these meetups could provide a nice checkpoint to 
see how we are doing with regards to the items listed below.

Please take a moment, scan through the list, ask questions, and/or send out 
additional areas that you feel the CloudStack Community should be focusing on.

If you were present at the hackathon, feel free to update us on what progress 
you might have made at the hackathon with regards to any topic below.

Thanks!
Mike

Hyper-V enlightenment

Version 5.x of CloudStack

KVM IO bursting

Live VM Migration

RPC Standard interface to VR

Getting INFO easily out of the SSVM

Deprecate old code (OVM?)

CloudMonkey testing

NoVNC in CPVM

CentOS SIG + packaging

VR Programming Optimization

New UI working with API Discovery

Network Models refactoring + designer UI

Marketing Plan

Video series for CloudStack (ex. developers series, users series)

Use GitHub to document aspects of CloudStack (how to build an environment, how 
to start writing code for it, etc.)

Figure out a process for how we'd like issues to be opened, assigned, closed, 
and resolved (using JIRA and GitHub Issues)

Create a true REST API (it can use the existing API behind the scenes).

Logic to generate code in particular use cases so you can focus mainly on your 
business logic.

Use standard libraries that implement JPA, HTTP, etc.

Remote Meetups every quarter

Support IPv6

Re: CloudStack Collab in Brazil

[Tutkowski, Mike]

I would be really interested in an event in Brazil.


From: Rafael Weingärtner 
Sent: Monday, October 1, 2018 5:38 AM
To: users
Cc: dev
Subject: Re: CloudStack Collab in Brazil

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.




Hey Marco,
Yes, they run a very successful conference every year. I have just got back
from Montreal, and I talked with people there regarding the conference.

Now, for all CloudStackers (users and devs); I will repeat what I said in
Montreal. The TDC conference will happen with or without us. Therefore, we
only need to decide if we will join them in their Cloud tracks. We did not
hear much feedback here, but I will try again.

If you are part of the CloudStack community (as a contributor, committer,
user, operator, and so on), please do provide your feedback. Would you like
to see a CloudStack Collab Conference in Florianopolis, Brazil, 2019? I am
only asking you guys, what you think. I do understand the logistics
problems for some folks to attend a conference this far.

Now, about the city; the island has an airport (airport code = FLN).
However, most flights to FLN will have a connection either on GRU (Sao
Paulo airport) or GIG (Rio de Janeiro airport); KLM, AA, Delta, AirFrance,
Tap, and others have flights to FLN. I have also found some useful links in
English that can be used by your guys to check the city. In this link [1]
you can information not only about the city, but the State as well; there
are pages in different languages such as English, Spanish, and German (to
change the language there is a button in the top-right corner). On these
other links [2-3], you can find a guide (English only) of the city; it
contains a brief overview and some details about Museums, Beaches, events
and so on.

I would also be happy to answer any other question that you might have.

[1] http://turismo.sc.gov.br/en/cidade/florianopolis/#
[2] https://www.floripa-guide.com/attractions/about-florianopolis.html
[3] http://www.vivendofloripa.com.br/en/home/

On Tue, Sep 25, 2018 at 5:42 PM Marco Sinhoreli <
marco.sinhor...@shapeblue.com> wrote:

> Hello Rafael,
>
> I know this conference, last year in TDC Porto Alegre I spoke about ACS
> and ansible.
>
> I was very impressed with them event support and organization, they have a
> nice approach involving community in the organization. They also have a
> good penetration to prospect sponsors.
>
> I am able to help you in this subject since I am in Brazil as well.
>
> Best regards,
>
> Marco Sinhoreli
> marco.sinhor...@shapeblue.com
> mobile: +55 21 98276 3636
>
> Av. Brigadeiro Faria Lima, 3144 - 2º andar – Jardim
> Paulistano, São Paulo, SP, Brasil, 01451-000
> Phone: + 55 11 3568-2877
> http://www.shapeblue.com/ | twitter: @shapeblue
>
> Em 21/09/2018 08:37, "Rafael Weingärtner" 
> escreveu:
>
> Hello fellow devs and users (pardon me for the cross post),
>
> I already contacted the PMC on this matter, and I am now opening the
> discussion to the whole community. Let’s see what you guys think about
> a
> CloudStack conference in Brazil, and let’s work to make it happen ;)
>
> Since the rather shameful? situation with the CloudStack Collab
> Conference
> (CCC) in Brazil last year, I have been looking for possible ways to
> enable
> the event. And, it seems that I found it, and it is something that we
> are
> already used to do.
>
> There is a conference series in Brazil called TDC (The Developer’s
> conference) [1]. They run three conferences a year (Florianopolis, São
> Paulo, and Porto Alegre). They have been running for over a decade
> now. I
> attended the last one in São Paulo (July 2018) and it was awesome. To
> give
> you guys some numbers for the São Paulo event:
>
> - 4524 attendants
> - 6040 online-viewers (some talks are live streamed)
> - 2927 corporate registrations
> - 63 different tracks, and more than 300 talks.
> - 5 days of conference (Tuesday-Saturday)
>
> They are in the process of internationalizing the conference now. The
> hot
> site is being translated, and they are preparing things for
> English/Spanish
> CFPs and tracks. While talking with one of the organizers during the
> event,
> I mentioned that we have been doing collocated CCC with ApacheCon and
> that
> I would love to see CCC in Brazil. Ant it turns out, they would love
> to see
> us there in Brazil as well. They offered to provide the same support as
> ApacheCon provides us. We would only need to organize the CFP and
> selection of the presentations. We would also need to tell them our
> needs:
> rooms, hackathon spaces, and so on. They are proposing for us space in
> their Florianopolis TDC 2019, which will be held in Florianopolis
> city. The
> event will take place in April 2019 (there is not a possibility for the
> event to be canceled this time!).
>
> I can coordinate this process with them, but I might need some help
> 

Exception in MS on master

[Tutkowski, Mike]

Hi everyone,

I was building a new cloud and came across the following exception when running 
the management server (below).

Any thoughts on what this is about?

Thanks!
Mike

WARN  [o.a.c.e.o.NetworkOrchestrator] (Network-Scavenger-1:ctx-8cd291c0) 
(logid:4f70c744) Caught exception while running network gc:
com.cloud.utils.exception.CloudRuntimeException: Caught: 
com.mysql.jdbc.JDBC4PreparedStatement@6ffe01cc: SELECT networks.id FROM 
networks  INNER JOIN network_offerings ON 
networks.network_offering_id=network_offerings.id  INNER JOIN op_networks ON 
networks.id=op_networks.id WHERE networks.removed IS NULL  AND  
(op_networks.nics_count = ** NOT SPECIFIED **  AND op_networks.gc = ** NOT 
SPECIFIED **  AND op_networks.check_for_gc = ** NOT SPECIFIED ** )
at 
com.cloud.utils.db.GenericDaoBase.customSearchIncludingRemoved(GenericDaoBase.java:507)
at com.cloud.utils.db.GenericDaoBase.customSearch(GenericDaoBase.java:518)
at 
com.cloud.network.dao.NetworkDaoImpl.findNetworksToGarbageCollect(NetworkDaoImpl.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:338)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:197)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:174)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
at com.sun.proxy.$Proxy96.findNetworksToGarbageCollect(Unknown Source)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.reallyRun(NetworkOrchestrator.java:2761)
at 
org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2745)
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 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
com.cloud.utils.db.GenericDaoBase.prepareAttribute(GenericDaoBase.java:1519)
at 
com.cloud.utils.db.GenericDaoBase.addJoinAttributes(GenericDaoBase.java:774)
at 
com.cloud.utils.db.GenericDaoBase.customSearchIncludingRemoved(GenericDaoBase.java:476)
... 29 more

Re: Another GUI Issue on master

[Tutkowski, Mike]

That looks like the issue I was seeing – thanks!

On 8/27/18, 7:45 PM, "Rafael Weingärtner"  wrote:

Can you check this PR https://github.com/apache/cloudstack/pull/2803?

There was the jQuery-UI upgrade. I think PRs coming from 4.11 branch are
causing these problems. The new jQuery UI requires us to handle the closing
of modal popups in a different manner.

On Mon, Aug 27, 2018 at 5:15 PM, Tutkowski, Mike 
wrote:

> Hi everyone,
>
> I’ve encountered another GUI issue on master: https://imgur.com/a/RCLPAfB.
>
> This one appears when I try to perform a cross-cluster VM migration on
> XenServer.
>
> We seem to have regressed quite a bit with regards to the GUI on master
> (this is one of around 3 issues that have popped up this release related 
to
> the GUI). Did we swap in a new GUI library or something that is 
responsible
> for all of these issues?
>
> Thanks,
> Mike
>



-- 
Rafael Weingärtner

Another GUI Issue on master

[Tutkowski, Mike]

Hi everyone,

I’ve encountered another GUI issue on master: https://imgur.com/a/RCLPAfB.

This one appears when I try to perform a cross-cluster VM migration on 
XenServer.

We seem to have regressed quite a bit with regards to the GUI on master (this 
is one of around 3 issues that have popped up this release related to the GUI). 
Did we swap in a new GUI library or something that is responsible for all of 
these issues?

Thanks,
Mike

Re: advice needed: snapshot DB/table cleanup

[Tutkowski, Mike]

Hi Andrija,

I like the way you wrote your SQL for the cloud.snapshots_store_ref table. It 
will make sure SolidFire snapshots remain in that table. Even if some of those 
are in the Deleted state, that’s OK. Perhaps the system will clean them up as 
expected in newer versions of CloudStack (otherwise, you can always delete them 
later).

Also, your plan for marking deleted snapshots as deleted with a removed date 
sounds good to me.

Talk to you later!
Mike

On 8/17/18, 9:39 AM, "Andrija Panic"  wrote:

Hi Daan, thx for the reply,

so yes I would not touch SF just for sake of magic, whatever - otherwise I
can remove them in same fashion (.

the second "is this the same" - its not -first SQL -  I delete from
snapshot_store_ref where the template is either DESTROYED or has REMOVED
date set in the main "snapshots" table. then later I just make sure (2nd
SQL) in the main "snapshot" table that if either the REMOVED or DESTROYED
is set - that I also set the missing value :) (previously all store_ref is
gone because of 1st SQL...)

As for the garbage, this has been happening from 4.5 up to now 4.8 for good
knows what reason - you remove something, and either status is set to
DESTROYED with no removal date (mostly its only for snapsbots, I don't
recall seen it on other resources) or removed date is set but state is
still READY (I actually just recently seen this and only on snaposhots -
can't be sure if this is because of ACS, or because of someone changing DB
(in case of snaps are in ERROR or ALLOCATED state - then you simply have to
alter DB, no way to cleanup via API). When you deal with CEPH and
long-running snaphosts than different gremlins can happen from time to time
- my experience at least...


Hope that makes sense (my answers)

Cheers
ANdrija

On Fri, 17 Aug 2018 at 16:40, Daan Hoogland  wrote:

> andrija,
>
> On Fri, Aug 17, 2018 at 11:23 AM, Andrija Panic 
> wrote:
>
> > HI guys, hi Mike.T.,
> >
> > we have removed all NFS and CEPH storages, and are now purely running on
> > SolidFire (KVM).
> >
> > Now I want to do serious snapshot cleanup (for reason explained at the
> end
> > of email) - since "snapshots" and "snapshot_store_ref" tables are a
> > complete mess (i.e. snapshot is destroyed with/without "removed" date,
> and
> > then there are still references in snapshot_store_ref to these 
fully/half
> > destroyed snapshots...)
> >
> > I would like to ask for a tip - based on my common sense and experience,
> I
> > was thinking on doing something like following:
> >
> > SQL:
> > delete from snapshot_store_ref where snapshot_id in (select id from
> > snapshots where status="destroyed" or removed is NOT NULL and min_iops 
is
> > NULL)
> >
> why the do you want to keep the solidfire snapshots when removed?
>
>
>
> >
> > This last "min_iops is NULL" is identifier for snaps that are NOT on
> > SolidFire - I would not touch SF snapshots) - i.e. all snapshots that 
are
> > created from SF volumes have min_iops and max_iops values set - so I 
just
> > exclude them here
> >
> > - So - above I want to remove all references for snapshots that are
> > fully/semi destroyed (status=destroyed but no removed date - or other 
way
> > around - those that have "removed" date but status=Ready.)
> >
> isn't this the same as below?
>
>
>
> >
> > Then I was also thinking does it make sense, to also set (in "snapshots"
> > table) status=Destroyed where removed is NOT NULL and other way around -
> > set removed date where status=Destroyed.
> >
> isn't this the same as above?
>
>
> Also when having cleaned all snapshots that are not for solidfire I would
> first do a check as your mess should be largely cleaned by then.
> and if a few snapshots still jump out better investigate those to see if
> you can find any root cause for the failure.
>
>
> > Sorry for long question - but I had issues with some snaps referencing
> CEPH
> > (and we removed CEPH/NFS from ACS GUI) - i.e. client was unable to list
> > snaps for his account, because some volumes had snaps that were
> referencing
> > CEPH (though they are migrated to SF or deleted)...
> >
> > Thanks a lot
> >
> hope my loose hipshots help,
>
>
>
> >
> > Andrija
> >
> >
> >
> > --
> >
> > Andrija Panić
> >
>
>
>
> --
> Daan
>


-- 

Andrija Panić

Re: [DISCUSS] Release effort for 4.11.2.0

[Tutkowski, Mike]

This sounds good to me, Rohit.

Also, I would like to add this bug to the list for 4.11.2.0:

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

On 8/2/18, 2:57 AM, "Rohit Yadav"  wrote:

All,


The recent CloudStack 4.11.1.0 release received a good reception but this 
thread is to gather feedback especially list of bugs and issues from the 
community that we should aim to fix towards the next minor LTS 4.11.2.0 release.


Here is a rough timeline proposal for the same:


0-4 week: Get feedback from the community, gather and triage list of 
issues, start fixing/testing/reviewing them

4-6 week: Stabilize 4.11 branch towards 4.11.2.0, cut RC and start voting

6-8 week: Iterate over RCs/voting and release!


To limit the scope for RM, blocker/critical issues will take priority. Paul 
will continue as RM for the 4.11.2.0 release, with assistance from Boris, Daan, 
and myself.


For reference, this is the 4.11.2.0 milestone PR/issues list:

https://github.com/apache/cloudstack/milestone/6


Thoughts, issues you want to discuss, feedback? Thanks.


- Rohit

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: GUI Wizard Issue on master

[Tutkowski, Mike]

Thanks! I can take a look at that PR.

> On Aug 2, 2018, at 10:39 AM, Rafael Weingärtner  
> wrote:
> 
> It seems to be a problem caused by the upgrade of jQuery-UI. It looks like
> jQuery UI is handling differently the creation of those divs. Can you take
> a look at my PR: https://github.com/apache/cloudstack/pull/2787?
> 
> On Wed, Aug 1, 2018 at 6:30 PM, Tutkowski, Mike 
> wrote:
> 
>> Also, there seems to be a weird outline around the Create Instance wizard,
>> as well.
>> 
>> On 8/1/18, 3:28 PM, "Tutkowski, Mike"  wrote:
>> 
>>Here’s what it looks like:
>> 
>>https://imgur.com/a/cV7pc9L
>> 
>>On 8/1/18, 3:25 PM, "Tutkowski, Mike" 
>> wrote:
>> 
>>I don’t have Firefox installed, but I see the same problem on both
>> Chrome and Safari.
>> 
>>On 8/1/18, 3:18 PM, "Rafael Weingärtner" <
>> rafaelweingart...@gmail.com> wrote:
>> 
>>Are you seeing this only with Chrome? Or is it the same in
>> Firefox as well?
>> 
>>On Wed, Aug 1, 2018 at 6:13 PM, Tutkowski, Mike <
>> mike.tutkow...@netapp.com>
>>wrote:
>> 
>>> Hi,
>>> 
>>> Has anyone else noticed that the Create Zone wizard’s
>> navigation buttons
>>> are placed below the bottom edge of the wizard? I just saw
>> this on master
>>> today using Chrome.
>>> 
>>> Thanks,
>>> Mike
>>> 
>> 
>> 
>> 
>>--
>>Rafael Weingärtner
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> Rafael Weingärtner

Re: [GitHub] rafaelweingartner commented on issue #2761: Add managed storage pool constraints to MigrateWithVolume API method

[Tutkowski, Mike]

Sure, it’s no rush for me.

Just let me know when you’re ready for me to merge it or feel free to merge it 
yourself.

> On Aug 2, 2018, at 5:08 AM, GitBox  wrote:
> 
> rafaelweingartner commented on issue #2761: Add managed storage pool 
> constraints to MigrateWithVolume API method
> URL: https://github.com/apache/cloudstack/pull/2761#issuecomment-409890686
> 
> 
>   @DaanHoogland that is what I was going to say to Mike. We can squash at the 
> merge "moment".
> 
>   Can we wait more one week or so before merging? I would like to cover this 
> code with unit tests. It is a very complicated and delicate one code, and it 
> does not have unit-tests for it.
> 
> 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on GitHub and use the
> URL above to go to the specific comment.
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 
> With regards,
> Apache Git Services

Re: GUI Wizard Issue on master

[Tutkowski, Mike]

Also, there seems to be a weird outline around the Create Instance wizard, as 
well.

On 8/1/18, 3:28 PM, "Tutkowski, Mike"  wrote:

Here’s what it looks like:

https://imgur.com/a/cV7pc9L

On 8/1/18, 3:25 PM, "Tutkowski, Mike"  wrote:

I don’t have Firefox installed, but I see the same problem on both 
Chrome and Safari.

On 8/1/18, 3:18 PM, "Rafael Weingärtner"  
wrote:

Are you seeing this only with Chrome? Or is it the same in Firefox 
as well?

On Wed, Aug 1, 2018 at 6:13 PM, Tutkowski, Mike 

wrote:

> Hi,
>
> Has anyone else noticed that the Create Zone wizard’s navigation 
buttons
> are placed below the bottom edge of the wizard? I just saw this 
on master
> today using Chrome.
>
> Thanks,
> Mike
>



-- 
Rafael Weingärtner

Re: GUI Wizard Issue on master

[Tutkowski, Mike]

Here’s what it looks like:

https://imgur.com/a/cV7pc9L

On 8/1/18, 3:25 PM, "Tutkowski, Mike"  wrote:

I don’t have Firefox installed, but I see the same problem on both Chrome 
and Safari.

On 8/1/18, 3:18 PM, "Rafael Weingärtner"  
wrote:

Are you seeing this only with Chrome? Or is it the same in Firefox as 
well?

On Wed, Aug 1, 2018 at 6:13 PM, Tutkowski, Mike 

wrote:

> Hi,
>
> Has anyone else noticed that the Create Zone wizard’s navigation 
buttons
> are placed below the bottom edge of the wizard? I just saw this on 
master
> today using Chrome.
>
> Thanks,
> Mike
>



-- 
Rafael Weingärtner

Re: GUI Wizard Issue on master

[Tutkowski, Mike]

I don’t have Firefox installed, but I see the same problem on both Chrome and 
Safari.

On 8/1/18, 3:18 PM, "Rafael Weingärtner"  wrote:

Are you seeing this only with Chrome? Or is it the same in Firefox as well?

On Wed, Aug 1, 2018 at 6:13 PM, Tutkowski, Mike 
wrote:

> Hi,
>
> Has anyone else noticed that the Create Zone wizard’s navigation buttons
> are placed below the bottom edge of the wizard? I just saw this on master
> today using Chrome.
>
> Thanks,
> Mike
>



-- 
Rafael Weingärtner

GUI Wizard Issue on master

[Tutkowski, Mike]

Hi,

Has anyone else noticed that the Create Zone wizard’s navigation buttons are 
placed below the bottom edge of the wizard? I just saw this on master today 
using Chrome.

Thanks,
Mike

Re: [GitHub] rafaelweingartner commented on a change in pull request #2761: Add managed storage pool constraints to MigrateWithVolume API method

[Tutkowski, Mike]

That is correct (that is how the old behavior worked).

On 7/25/18, 2:56 PM, "GitBox"  wrote:

rafaelweingartner commented on a change in pull request #2761: Add managed 
storage pool constraints to MigrateWithVolume API method
URL: https://github.com/apache/cloudstack/pull/2761#discussion_r205259766
 
 

 ##
 File path: 
engine/orchestration/src/main/java/com/cloud/vm/VirtualMachineManagerImpl.java
 ##
 @@ -2282,7 +2282,7 @@ protected void migrate(final VMInstanceVO vm, final 
long srcHostId, final Deploy
  * Create the mapping of volumes and storage pools. If the user did 
not enter a mapping on her/his own, we create one using {@link 
#getDefaultMappingOfVolumesAndStoragePoolForMigration(VirtualMachineProfile, 
Host)}.
  * If the user provided a mapping, we use whatever the user has 
provided (check the method {@link 
#createMappingVolumeAndStoragePoolEnteredByUser(VirtualMachineProfile, Host, 
Map)}).
  */
-private Map 
getPoolListForVolumesForMigration(VirtualMachineProfile profile, Host 
targetHost, Map volumeToPool) {
+protected Map 
getPoolListForVolumesForMigration(VirtualMachineProfile profile, Host 
targetHost, Map volumeToPool) {
 
 Review comment:
   Ok, so to summarize. If the VM has two volumes, you want to be able to 
define the migration for one of them and the other that was not specified 
should be taken care by ACS. Is that it? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

***UNCHECKED*** Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Thanks, Rafael – I should be able to take a look at this later today.

On 7/23/18, 6:58 AM, "Rafael Weingärtner"  wrote:

Hey Mike, PR created: https://github.com/apache/cloudstack/pull/2761
Can you take a look at it?

On Tue, Jul 17, 2018 at 4:35 PM, Tutkowski, Mike 
wrote:

> Correct, I happened to find it while testing a PR of mine targeted at
> master.
>
> > On Jul 17, 2018, at 1:30 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
> >
> > Correct. I do think the problem here is only in the release notes.
> >
> > Just to confirm, you found the problem while testing 4.12 (from master),
> > right?
> >
> > On Tue, Jul 17, 2018 at 4:22 PM, Tutkowski, Mike <
> mike.tutkow...@netapp.com>
> > wrote:
> >
> >> Cool, if it’s just in master, then that makes it easier.
> >>
> >> Also, it means we did not have a process issue by introducing
> enhancement
> >> code in between release candidates.
> >>
> >> It would mean, however, that our documentation is a bit incorrect if, 
in
> >> fact, it states that that feature exists in 4.11.1.
> >>
> >>> On Jul 17, 2018, at 1:20 PM, Rafael Weingärtner <
> >> rafaelweingart...@gmail.com> wrote:
> >>>
    > >>> Ok, thanks. I had the impression that we said it was backported to
> 4.11.
> >>>
> >>> I will get master and work on it then.
> >>>
> >>> On Tue, Jul 17, 2018 at 4:12 PM, Tutkowski, Mike <
> >> mike.tutkow...@netapp.com>
> >>> wrote:
> >>>
> >>>> I only noticed it in master. The example code I was comparing it
> against
> >>>> was from 4.11.0. I never checked against 4.11.1.
> >>>>
> >>>>> On Jul 17, 2018, at 1:02 PM, Rafael Weingärtner <
> >>>> rafaelweingart...@gmail.com> wrote:
> >>>>>
> >>>>> Hey Mike, I got the branch 4.11 to start fixing the problem we
> >> discussed,
> >>>>> but I do not think my commit was backported to 4.11. I mean, I am at
> >>>>> "VirtualMachineManagerImpl" and the code is not here. I also checked
> >> the
> >>>>> commit (
> >>>>> https://github.com/apache/cloudstack/commit/
> >>>> f2efbcececb3cfb06a51e5d3a2e77417c19c667f)
> >>>>> that introduced those changes to master, and according to Github, it
> is
> >>>>> only in the master branch, and not in 4.11.
> >>>>>
> >>>>> I checked the "VirtualMachineManagerImpl" class at the Apache
> >> CloudStack
> >>>>> remote repository in the 4.11 branch, and as you can see, the code
> >> there
> >>>> is
> >>>>> the “old”   one.
> >>>>> https://github.com/apache/cloudstack/blob/4.11/engine/
> >>>> orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java
> >>>>>
> >>>>> I got a little confused now. Did you detect the problem in 4.11 or 
in
> >>>>> master?
> >>>>>
> >>>>>
> >>>>> On Tue, Jul 17, 2018 at 12:27 AM, Tutkowski, Mike <
> >>>> mike.tutkow...@netapp.com
> >>>>>> wrote:
> >>>>>
> >>>>>> Another comment here: The part that is broken is if you try to let
> >>>>>> CloudStack pick the primary storage on the destination side. That
> code
> >>>> no
> >>>>>> longer exists in 4.11.1.
> >>>>>>
> >>>>>> On 7/16/18, 9:24 PM, "Tutkowski, Mike" 
> >>>> wrote:
> >>>>>>
> >>>>>>  To follow up on this a bit: Yes, you should be able to migrate a 
VM
> >>>>>> and its storage from one cluster to another today using non-managed
> >>>>>> (traditional) primary storage with XenServer (both the source and
> >>>>>> destination primary storages would be cluster scoped). However, 
that
> >> is
> >>>> one
> >>>>>> of the features that was broken in 4.11.1 tha

Re: [PROPOSE] Combining Apache CloudStack Documentation

[Tutkowski, Mike]

I like this, too, Paul.

On 7/24/18, 4:01 AM, "ilya musayev"  wrote:

I like it but wonder if Upgrade section needs to be added? ..

On Tue, Jul 24, 2018 at 2:25 AM Paul Angus  wrote:

> Hi All,
>
> We currently have four sources of documentation [1]. Which make managing
> the documentation convoluted, and worse, make navigating and searching the
> documentation really difficult.
>
> I have taken the current documentation and combined them into one repo,
> then created 7 sections:
>
> CloudStack Concepts and Terminology
> Quick Installation Guide
> Installation Guide
> Usage Guide
> Developers Guide
> Plugins Guide
> Release Notes
>
> I haven't changed any of the content, but I've moved some of it around to
> make more sense (to me).  You can see the result on RTD [2]
>
> I'd like to PROPOSE to move this demo version of the documentation over to
> the Apache repos and make it THE documentation source, update the website,
> and mark the current repos/sites as archive data.
>
> [1]
> https://github.com/apache/cloudstack-docs.git <
> https://github.com/apache/cloudstack-docs.git> is a bit of a dodge-podge
> of resources
> https://github.com/apache/cloudstack-docs-install.git is the install guide
> https://github.com/apache/cloudstack-docs-admin.git is the current admin
> manual.
> https://github.com/apache/cloudstack-docs-rn.git is the release notes for
> individual releases
>
> [2]  https://beta-cloudstack-docs.readthedocs.io/en/latest/
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
>

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Correct, I happened to find it while testing a PR of mine targeted at master.

> On Jul 17, 2018, at 1:30 PM, Rafael Weingärtner  
> wrote:
> 
> Correct. I do think the problem here is only in the release notes.
> 
> Just to confirm, you found the problem while testing 4.12 (from master),
> right?
> 
> On Tue, Jul 17, 2018 at 4:22 PM, Tutkowski, Mike 
> wrote:
> 
>> Cool, if it’s just in master, then that makes it easier.
>> 
>> Also, it means we did not have a process issue by introducing enhancement
>> code in between release candidates.
>> 
>> It would mean, however, that our documentation is a bit incorrect if, in
>> fact, it states that that feature exists in 4.11.1.
>> 
>>> On Jul 17, 2018, at 1:20 PM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>> 
>>> Ok, thanks. I had the impression that we said it was backported to 4.11.
>>> 
>>> I will get master and work on it then.
>>> 
>>> On Tue, Jul 17, 2018 at 4:12 PM, Tutkowski, Mike <
>> mike.tutkow...@netapp.com>
>>> wrote:
>>> 
>>>> I only noticed it in master. The example code I was comparing it against
>>>> was from 4.11.0. I never checked against 4.11.1.
>>>> 
>>>>> On Jul 17, 2018, at 1:02 PM, Rafael Weingärtner <
>>>> rafaelweingart...@gmail.com> wrote:
>>>>> 
>>>>> Hey Mike, I got the branch 4.11 to start fixing the problem we
>> discussed,
>>>>> but I do not think my commit was backported to 4.11. I mean, I am at
>>>>> "VirtualMachineManagerImpl" and the code is not here. I also checked
>> the
>>>>> commit (
>>>>> https://github.com/apache/cloudstack/commit/
>>>> f2efbcececb3cfb06a51e5d3a2e77417c19c667f)
>>>>> that introduced those changes to master, and according to Github, it is
>>>>> only in the master branch, and not in 4.11.
>>>>> 
>>>>> I checked the "VirtualMachineManagerImpl" class at the Apache
>> CloudStack
>>>>> remote repository in the 4.11 branch, and as you can see, the code
>> there
>>>> is
>>>>> the “old”   one.
>>>>> https://github.com/apache/cloudstack/blob/4.11/engine/
>>>> orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java
>>>>> 
>>>>> I got a little confused now. Did you detect the problem in 4.11 or in
>>>>> master?
>>>>> 
>>>>> 
>>>>> On Tue, Jul 17, 2018 at 12:27 AM, Tutkowski, Mike <
>>>> mike.tutkow...@netapp.com
>>>>>> wrote:
>>>>> 
>>>>>> Another comment here: The part that is broken is if you try to let
>>>>>> CloudStack pick the primary storage on the destination side. That code
>>>> no
>>>>>> longer exists in 4.11.1.
>>>>>> 
>>>>>> On 7/16/18, 9:24 PM, "Tutkowski, Mike" 
>>>> wrote:
>>>>>> 
>>>>>>  To follow up on this a bit: Yes, you should be able to migrate a VM
>>>>>> and its storage from one cluster to another today using non-managed
>>>>>> (traditional) primary storage with XenServer (both the source and
>>>>>> destination primary storages would be cluster scoped). However, that
>> is
>>>> one
>>>>>> of the features that was broken in 4.11.1 that we are discussing in
>> this
>>>>>> thread.
>>>>>> 
>>>>>>  On 7/16/18, 9:20 PM, "Tutkowski, Mike" 
>>>>>> wrote:
>>>>>> 
>>>>>>  For a bit of info on what managed storage is, please take a look
>>>>>> at this document:
>>>>>> 
>>>>>>  https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%
>>>>>> 20in%20CloudStack.docx?dl=0
>>>>>> 
>>>>>>  The short answer is that you can have zone-wide managed storage
>>>>>> (for XenServer, VMware, and KVM). However, there is no current
>> zone-wide
>>>>>> non-managed storage for XenServer.
>>>>>> 
>>>>>>  On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:
>>>>>> 
>>>>>>  I assume by "managed storage", you guys mean primary
>>>> storages,
>>>>>> either zone -wide or cluster-wide.
>>>>>> 
>>>>>>  For Xen hypervisor, ACS does not support "zone-wide" primary
>>>>>> storage yet. Still, I can live migrate a VM with data disks between
>>>>>> clusters with storage migration from web GUI, today.  So, your
>> statement
>>>>>> below does not reflect current behavior of the code.
>>>>>> 
>>>>>> 
>>>>>> - If I want to migrate a VM across clusters, but
>>>> if
>>>>>> at least one of its
>>>>>> volumes is placed in a cluster-wide managed
>>>>>> storage, the migration is not
>>>>>> allowed. Is that it?
>>>>>> 
>>>>>>  [Mike] Correct
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Rafael Weingärtner
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>> 
> 
> 
> 
> -- 
> Rafael Weingärtner

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Cool, if it’s just in master, then that makes it easier.

Also, it means we did not have a process issue by introducing enhancement code 
in between release candidates.

It would mean, however, that our documentation is a bit incorrect if, in fact, 
it states that that feature exists in 4.11.1.

> On Jul 17, 2018, at 1:20 PM, Rafael Weingärtner  
> wrote:
> 
> Ok, thanks. I had the impression that we said it was backported to 4.11.
> 
> I will get master and work on it then.
> 
> On Tue, Jul 17, 2018 at 4:12 PM, Tutkowski, Mike 
> wrote:
> 
>> I only noticed it in master. The example code I was comparing it against
>> was from 4.11.0. I never checked against 4.11.1.
>> 
>>> On Jul 17, 2018, at 1:02 PM, Rafael Weingärtner <
>> rafaelweingart...@gmail.com> wrote:
>>> 
>>> Hey Mike, I got the branch 4.11 to start fixing the problem we discussed,
>>> but I do not think my commit was backported to 4.11. I mean, I am at
>>> "VirtualMachineManagerImpl" and the code is not here. I also checked the
>>> commit (
>>> https://github.com/apache/cloudstack/commit/
>> f2efbcececb3cfb06a51e5d3a2e77417c19c667f)
>>> that introduced those changes to master, and according to Github, it is
>>> only in the master branch, and not in 4.11.
>>> 
>>> I checked the "VirtualMachineManagerImpl" class at the Apache CloudStack
>>> remote repository in the 4.11 branch, and as you can see, the code there
>> is
>>> the “old”   one.
>>> https://github.com/apache/cloudstack/blob/4.11/engine/
>> orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java
>>> 
>>> I got a little confused now. Did you detect the problem in 4.11 or in
>>> master?
>>> 
>>> 
>>> On Tue, Jul 17, 2018 at 12:27 AM, Tutkowski, Mike <
>> mike.tutkow...@netapp.com
>>>> wrote:
>>> 
>>>> Another comment here: The part that is broken is if you try to let
>>>> CloudStack pick the primary storage on the destination side. That code
>> no
>>>> longer exists in 4.11.1.
>>>> 
>>>> On 7/16/18, 9:24 PM, "Tutkowski, Mike" 
>> wrote:
>>>> 
>>>>   To follow up on this a bit: Yes, you should be able to migrate a VM
>>>> and its storage from one cluster to another today using non-managed
>>>> (traditional) primary storage with XenServer (both the source and
>>>> destination primary storages would be cluster scoped). However, that is
>> one
>>>> of the features that was broken in 4.11.1 that we are discussing in this
>>>> thread.
>>>> 
>>>>   On 7/16/18, 9:20 PM, "Tutkowski, Mike" 
>>>> wrote:
>>>> 
>>>>   For a bit of info on what managed storage is, please take a look
>>>> at this document:
>>>> 
>>>>   https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%
>>>> 20in%20CloudStack.docx?dl=0
>>>> 
>>>>   The short answer is that you can have zone-wide managed storage
>>>> (for XenServer, VMware, and KVM). However, there is no current zone-wide
>>>> non-managed storage for XenServer.
>>>> 
>>>>   On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:
>>>> 
>>>>   I assume by "managed storage", you guys mean primary
>> storages,
>>>> either zone -wide or cluster-wide.
>>>> 
>>>>   For Xen hypervisor, ACS does not support "zone-wide" primary
>>>> storage yet. Still, I can live migrate a VM with data disks between
>>>> clusters with storage migration from web GUI, today.  So, your statement
>>>> below does not reflect current behavior of the code.
>>>> 
>>>> 
>>>>  - If I want to migrate a VM across clusters, but
>> if
>>>> at least one of its
>>>>  volumes is placed in a cluster-wide managed
>>>> storage, the migration is not
>>>>  allowed. Is that it?
>>>> 
>>>>   [Mike] Correct
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Rafael Weingärtner
>> 
> 
> 
> 
> -- 
> Rafael Weingärtner

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

I only noticed it in master. The example code I was comparing it against was 
from 4.11.0. I never checked against 4.11.1.

> On Jul 17, 2018, at 1:02 PM, Rafael Weingärtner  
> wrote:
> 
> Hey Mike, I got the branch 4.11 to start fixing the problem we discussed,
> but I do not think my commit was backported to 4.11. I mean, I am at
> "VirtualMachineManagerImpl" and the code is not here. I also checked the
> commit (
> https://github.com/apache/cloudstack/commit/f2efbcececb3cfb06a51e5d3a2e77417c19c667f)
> that introduced those changes to master, and according to Github, it is
> only in the master branch, and not in 4.11.
> 
> I checked the "VirtualMachineManagerImpl" class at the Apache CloudStack
> remote repository in the 4.11 branch, and as you can see, the code there is
> the “old”   one.
> https://github.com/apache/cloudstack/blob/4.11/engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java
> 
> I got a little confused now. Did you detect the problem in 4.11 or in
> master?
> 
> 
> On Tue, Jul 17, 2018 at 12:27 AM, Tutkowski, Mike > wrote:
> 
>> Another comment here: The part that is broken is if you try to let
>> CloudStack pick the primary storage on the destination side. That code no
>> longer exists in 4.11.1.
>> 
>> On 7/16/18, 9:24 PM, "Tutkowski, Mike"  wrote:
>> 
>>To follow up on this a bit: Yes, you should be able to migrate a VM
>> and its storage from one cluster to another today using non-managed
>> (traditional) primary storage with XenServer (both the source and
>> destination primary storages would be cluster scoped). However, that is one
>> of the features that was broken in 4.11.1 that we are discussing in this
>> thread.
>> 
>>On 7/16/18, 9:20 PM, "Tutkowski, Mike" 
>> wrote:
>> 
>>For a bit of info on what managed storage is, please take a look
>> at this document:
>> 
>>https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%
>> 20in%20CloudStack.docx?dl=0
>> 
>>The short answer is that you can have zone-wide managed storage
>> (for XenServer, VMware, and KVM). However, there is no current zone-wide
>> non-managed storage for XenServer.
>> 
>>On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:
>> 
>>I assume by "managed storage", you guys mean primary storages,
>> either zone -wide or cluster-wide.
>> 
>>For Xen hypervisor, ACS does not support "zone-wide" primary
>> storage yet. Still, I can live migrate a VM with data disks between
>> clusters with storage migration from web GUI, today.  So, your statement
>> below does not reflect current behavior of the code.
>> 
>> 
>>   - If I want to migrate a VM across clusters, but if
>> at least one of its
>>   volumes is placed in a cluster-wide managed
>> storage, the migration is not
>>   allowed. Is that it?
>> 
>>[Mike] Correct
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> Rafael Weingärtner

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Another comment here: The part that is broken is if you try to let CloudStack 
pick the primary storage on the destination side. That code no longer exists in 
4.11.1.

On 7/16/18, 9:24 PM, "Tutkowski, Mike"  wrote:

To follow up on this a bit: Yes, you should be able to migrate a VM and its 
storage from one cluster to another today using non-managed (traditional) 
primary storage with XenServer (both the source and destination primary 
storages would be cluster scoped). However, that is one of the features that 
was broken in 4.11.1 that we are discussing in this thread.

On 7/16/18, 9:20 PM, "Tutkowski, Mike"  wrote:

For a bit of info on what managed storage is, please take a look at 
this document:


https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%20in%20CloudStack.docx?dl=0

The short answer is that you can have zone-wide managed storage (for 
XenServer, VMware, and KVM). However, there is no current zone-wide non-managed 
storage for XenServer.

On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:

I assume by "managed storage", you guys mean primary storages, 
either zone -wide or cluster-wide.

For Xen hypervisor, ACS does not support "zone-wide" primary 
storage yet. Still, I can live migrate a VM with data disks between clusters 
with storage migration from web GUI, today.  So, your statement below does not 
reflect current behavior of the code.


   - If I want to migrate a VM across clusters, but if at 
least one of its
   volumes is placed in a cluster-wide managed storage, the 
migration is not
   allowed. Is that it?

[Mike] Correct

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

To follow up on this a bit: Yes, you should be able to migrate a VM and its 
storage from one cluster to another today using non-managed (traditional) 
primary storage with XenServer (both the source and destination primary 
storages would be cluster scoped). However, that is one of the features that 
was broken in 4.11.1 that we are discussing in this thread.

On 7/16/18, 9:20 PM, "Tutkowski, Mike"  wrote:

For a bit of info on what managed storage is, please take a look at this 
document:


https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%20in%20CloudStack.docx?dl=0

The short answer is that you can have zone-wide managed storage (for 
XenServer, VMware, and KVM). However, there is no current zone-wide non-managed 
storage for XenServer.

On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:

I assume by "managed storage", you guys mean primary storages, either 
zone -wide or cluster-wide.

For Xen hypervisor, ACS does not support "zone-wide" primary storage 
yet. Still, I can live migrate a VM with data disks between clusters with 
storage migration from web GUI, today.  So, your statement below does not 
reflect current behavior of the code.


   - If I want to migrate a VM across clusters, but if at least 
one of its
   volumes is placed in a cluster-wide managed storage, the 
migration is not
   allowed. Is that it?

[Mike] Correct

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

For a bit of info on what managed storage is, please take a look at this 
document:

https://www.dropbox.com/s/wwz2bjpra9ykk5w/SolidFire%20in%20CloudStack.docx?dl=0

The short answer is that you can have zone-wide managed storage (for XenServer, 
VMware, and KVM). However, there is no current zone-wide non-managed storage 
for XenServer.

On 7/16/18, 6:20 PM, "Yiping Zhang"  wrote:

I assume by "managed storage", you guys mean primary storages, either zone 
-wide or cluster-wide.

For Xen hypervisor, ACS does not support "zone-wide" primary storage yet. 
Still, I can live migrate a VM with data disks between clusters with storage 
migration from web GUI, today.  So, your statement below does not reflect 
current behavior of the code.


   - If I want to migrate a VM across clusters, but if at least one 
of its
   volumes is placed in a cluster-wide managed storage, the 
migration is not
   allowed. Is that it?

[Mike] Correct

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Yeah, I just meant that was a workaround. As you pointed out, that workaround 
doesn’t make use of the migrateVirtualMachineWithVolume API command, though.

On 7/16/18, 5:23 PM, "Rafael Weingärtner"  wrote:

Thanks for the answers Mike. I will not be able to do it today, but I will
manage to do it this week. There is only one last doubt.

[Mike] At least for KVM, you can shut the VM down and perform an offline
migration
of the volume from managed storage to non-managed storage. It’s possible we
may
support such a similar behavior with other hypervisor types in the future.

[Rafael] I guess that we can shut down XenServer VMs and then migrate the
volumes later, right? However, the method in question here
(migrateVirtualMachineWithVolume) is not supposed to execute such steps, is
it?


On Mon, Jul 16, 2018 at 8:17 PM, Tutkowski, Mike 
wrote:

>- So, managed storage can be cluster and zone wide. Is that 
correct?
>
> [Mike] Correct
>
>- If I want to migrate a VM across clusters, but if at least one of
> its
>volumes is placed in a cluster-wide managed storage, the migration
> is not
>allowed. Is that it?
>
> [Mike] Correct
>
>- A volume placed in managed storage can never (at least not using
> this
>migrateWithVolume method) be migrated out of the storage pool it
> resides.
>is this statement right? Do you have alternative/other execution
> flow
>regarding this scenario?
>
> [Mike] At least for KVM, you can shut the VM down and perform an offline
> migration
> of the volume from managed storage to non-managed storage. It’s possible
> we may
> support such a similar behavior with other hypervisor types in the future.
>
>- When migrating a VM that does not have volumes in managed
> storage, it
>should be possible to migrate it cross clusters. Therefore, we
> should try
>to use the volume allocators to find a suitable storage pool for 
its
>volumes in the target cluster
>
> [Mike] It’s OK here if one or more of the volumes is on managed storage.
> The “trick” is
> that it needs to be on zone-wide managed storage that is visible to both
> the source and
> destination compute clusters. You cannot specify a new storage pool for
> any of these volumes
> (each must remain on its current, zone-wide primary storage).
>
> If you can add these new constraints into the code, I can review them
> later. I’m a bit
> pressed for time this week, so it might not be possible to do so right
> away. Thanks!
>
> On 7/16/18, 3:52 PM, "Rafael Weingärtner" 
> wrote:
>
> Thanks for your feedback Mike. I actually did not want to change this
> “migrateVirtualMachineWithVolume” API method. Everything started when
> we
> wanted to create a feature to allow volume placement overrides. This
> means,
> allowing root admins to place/migrate the volume to a storage pool 
that
> might not be “allowed” (according to its current disk offering). This
> feature was later expanded to allow changing the disk offering while
> executing a storage migration (this means allowing changes on volume’s
> QoS). Thus, creating a mechanism within ACS to allow disk offerings
> replacement (as opposed to DB intervention, which was the way it was
> being
> done so far). The rationale behind these extensions/enhancement is
> that the
> root admins are wise/experts (at least we expect them to be).
> Therefore,
> they know what they are doing when overriding or replacing a disk
> offering
> of a user.
>
> So, why am I changing this “migrateVirtualMachineWithVolume” API
> method?
> When we allowed that override procedure, it broke the migration of VMs
> that
> had volumes initially placed in NFS and then replaced (via override) 
in
> local storage. It had something to do with the way ACS was detecting
> if the
> VM has a local storage. Then, when I went to the method to fix it; it
> was
> very convoluted to read and understand. Therefore, I re-wrote, and I
> missed
> your use case. I am sorry for that. Moreover, I do intend to keep with
> the
> current code, as we already have other features developed on top of
> it, and
> this code is well documented and unit tested. It is only a matter of
> adding
&g

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

   - So, managed storage can be cluster and zone wide. Is that correct?

[Mike] Correct

   - If I want to migrate a VM across clusters, but if at least one of its
   volumes is placed in a cluster-wide managed storage, the migration is not
   allowed. Is that it?

[Mike] Correct

   - A volume placed in managed storage can never (at least not using this
   migrateWithVolume method) be migrated out of the storage pool it resides.
   is this statement right? Do you have alternative/other execution flow
   regarding this scenario?

[Mike] At least for KVM, you can shut the VM down and perform an offline 
migration 
of the volume from managed storage to non-managed storage. It’s possible we may 
support such a similar behavior with other hypervisor types in the future.

   - When migrating a VM that does not have volumes in managed storage, it
   should be possible to migrate it cross clusters. Therefore, we should try
   to use the volume allocators to find a suitable storage pool for its
   volumes in the target cluster

[Mike] It’s OK here if one or more of the volumes is on managed storage. The 
“trick” is 
that it needs to be on zone-wide managed storage that is visible to both the 
source and 
destination compute clusters. You cannot specify a new storage pool for any of 
these volumes 
(each must remain on its current, zone-wide primary storage).

If you can add these new constraints into the code, I can review them later. 
I’m a bit 
pressed for time this week, so it might not be possible to do so right away. 
Thanks!

On 7/16/18, 3:52 PM, "Rafael Weingärtner"  wrote:

Thanks for your feedback Mike. I actually did not want to change this
“migrateVirtualMachineWithVolume” API method. Everything started when we
wanted to create a feature to allow volume placement overrides. This means,
allowing root admins to place/migrate the volume to a storage pool that
might not be “allowed” (according to its current disk offering). This
feature was later expanded to allow changing the disk offering while
executing a storage migration (this means allowing changes on volume’s
QoS). Thus, creating a mechanism within ACS to allow disk offerings
replacement (as opposed to DB intervention, which was the way it was being
done so far). The rationale behind these extensions/enhancement is that the
root admins are wise/experts (at least we expect them to be). Therefore,
they know what they are doing when overriding or replacing a disk offering
of a user.

So, why am I changing this “migrateVirtualMachineWithVolume” API method?
When we allowed that override procedure, it broke the migration of VMs that
had volumes initially placed in NFS and then replaced (via override) in
local storage. It had something to do with the way ACS was detecting if the
VM has a local storage. Then, when I went to the method to fix it; it was
very convoluted to read and understand. Therefore, I re-wrote, and I missed
your use case. I am sorry for that. Moreover, I do intend to keep with the
current code, as we already have other features developed on top of it, and
this code is well documented and unit tested. It is only a matter of adding
your requirement there.

Now, let’s fix the problem. I will not point code here. I only want to
understand the idea for now.

   - So, managed storage can be cluster and zone wide. Is that correct?
   - If I want to migrate a VM across clusters, but if at least one of its
   volumes is placed in a cluster-wide managed storage, the migration is not
   allowed. Is that it?
   - A volume placed in managed storage can never (at least not using this
   migrateWithVolume method) be migrated out of the storage pool it resides.
   is this statement right? Do you have alternative/other execution flow
   regarding this scenario?
   - When migrating a VM that does not have volumes in managed storage, it
   should be possible to migrate it cross clusters. Therefore, we should try
   to use the volume allocators to find a suitable storage pool for its
   volumes in the target cluster

Are these all of the use cases that were left behind?

On Mon, Jul 16, 2018 at 5:36 PM, Tutkowski, Mike 
wrote:

> For your feature, Rafael, are you trying to support the migration of a VM
> that has local storage from one cluster to another or is intra-cluster
> migration of local storage sufficient?
>
> There is the migrateVolume API (you can pass in “live migrate” parameter):
>
> http://cloudstack.apache.org/api/apidocs-4.11/apis/migrateVolume.html
>
> There is also the migrateVirtualMachineWithVolume (one or more volumes).
> This is especially useful for moving a VM with its storage from one 
cluster
> to another:
>

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

I think I understand the confusion here.

Rafael’s code was put into 4.11.1, but not into the initial release candidate 
(RC). In fact, the most recent version of 4.11 that has been released is 
4.11.1. Somehow Rafael’s code (which is an enhancement) was merged into 4.11 
during the RC process. This is why my automated tests did not find it. I ran 
them against 4.11.1 RC1 and his code was put in after the first RC.

It looks like we had a bit of a process issue during the RC process as only bug 
fixes should be going into the next RC.

In any event, this means the documentation (at least in this regard) should be 
fine for 4.11.1. Also, no 4.11.2 (or 4.11.3) has been publicly released. We 
seem to have been getting those confused with RCs in our e-mail chain here.

On 7/16/18, 1:46 PM, "Yiping Zhang"  wrote:

Why is it listed as fixed in 4.11.1.0 in the release note, If the code only 
exist in 4.11.2?



On 7/16/18, 12:43 PM, "Tutkowski, Mike"  wrote:

OK, as Rafael noted, looks like it’s in 4.11.2. My regression tests 
were run against 4.11.1. I thought we only allowed bug fixes when going to a 
new RC, but it appears we are not strictly enforcing that rule.

On 7/16/18, 1:40 PM, "Tutkowski, Mike"  
wrote:

When I ran my suite of tests on 4.11.1, I did not encounter this 
issue. Also, looking at the code now, it appears this new code is first in 4.12.

On 7/16/18, 1:36 PM, "Yiping Zhang"  wrote:


Is this code already in ACS 4.11.1.0? 

CLOUDSTACK-10240 is listed as fixed in 4.11.1.0, according to 
release note here, 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/ja/master/fixed_issues.html,
 but in the JIRA ticket itself, the "fixed version/s" field says 4.12.

We are using XenServer clusters with shared NFS storages and I 
am about to migrate to ACS 4.11.1.0 from 4.9.3.0.  Since we move VM between 
clusters a lot, this is going to be a blocker for us.  Someone please confirm.

Thanks

Yiping

    
On 7/14/18, 11:20 PM, "Tutkowski, Mike" 
 wrote:

Hi,

While running managed-storage regression tests tonight, I 
noticed a problem that is not related to managed storage.

CLOUDSTACK-10240 is a ticket asking that we allow the 
migration of a virtual disk that’s on local storage to shared storage. In the 
process of enabling this feature, the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method was 
re-written in a way that completely breaks at least one use case: Migrating a 
VM across compute clusters (at least supported in XenServer). If, say, a 
virtual disk resides on shared storage in the source compute cluster, we must 
be able to copy this virtual disk to shared storage in the destination compute 
cluster.

As the code is currently written, this is no longer 
possible. It also seems that the managed-storage logic has been dropped for 
some reason in the new implementation.

Rafael – It seems that you worked on this feature. Would 
you be able to look into this and create a PR?

Thanks,
Mike

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

For your feature, Rafael, are you trying to support the migration of a VM that 
has local storage from one cluster to another or is intra-cluster migration of 
local storage sufficient?

There is the migrateVolume API (you can pass in “live migrate” parameter):

http://cloudstack.apache.org/api/apidocs-4.11/apis/migrateVolume.html

There is also the migrateVirtualMachineWithVolume (one or more volumes). This 
is especially useful for moving a VM with its storage from one cluster to 
another:

http://cloudstack.apache.org/api/apidocs-4.11/apis/migrateVirtualMachineWithVolume.html

On 7/16/18, 2:20 PM, "Tutkowski, Mike"  wrote:

Actually, I think I answered both of your questions with these two prior 
e-mails. Please let me know if you need further clarification. Thanks!

On 7/16/18, 2:17 PM, "Tutkowski, Mike"  wrote:

Allow me to correct what I said here:

“If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, we 
silently ignore the (faulty) input (which is a new storage pool) from the user 
and keep the volume in its same managed storage pool (the user may wonder why 
it wasn’t migrated if they don’t get an error message back telling them this is 
not allowed).”

I should have said the following:

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked on a 
VM that is using managed storage that is only at the cluster level (managed 
storage can be at either the zone or cluster level) and we are trying to 
migrate the VM from one cluster to another, this operation should fail (as the 
old code detects). The new code tries to keep the volume in the same storage 
pool (but that storage pool will not be visible to the hosts in the destination 
compute cluster).

On 7/16/18, 2:10 PM, "Tutkowski, Mike"  
wrote:

Let me answer the questions in two separate e-mails.

This answer deals with what you wrote about this code:

> if (destPool.getId() == currentPool.getId()) {
> volumeToPoolObjectMap.put(volume, currentPool);
> } else {
>  throw new CloudRuntimeException("Currently, a volume on 
managed
> storage can only be 'migrated' to itself.");
> }
>

The code above is invoked if the user tries to migrate a volume 
that’s on managed storage to another storage pool. At present, such volumes can 
be migrated when a VM is migrated from one compute cluster to another, but 
those volumes have to remain on the same managed storage.

Here’s an example:

Let’s say VM_1 is in Cluster_1. VM_1 has a root (or data) disk on 
managed storage. We try to migrate the VM from Cluster_1 to Cluster_2 and 
specify a new storage pool for the volume. This case should fail. To make it 
work, you need to either 1) not specify a new storage pool or 2) specify the 
same storage pool the volume is already in. If the managed storage in question 
is zone wide, then it can be used from both Cluster_1 and Cluster_2.

The new code might call 
getDefaultMappingOfVolumesAndStoragePoolForMigration (if no storage pools at 
all are passed in to the API) or it might call 
createMappingVolumeAndStoragePoolEnteredByUser.

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, 
we silently ignore the (faulty) input (which is a new storage pool) from the 
user and keep the volume in its same managed storage pool (the user may wonder 
why it wasn’t migrated if they don’t get an error message back telling them 
this is not allowed).

If createMappingVolumeAndStoragePoolEnteredByUser is invoked, we 
seem to have a bigger problem (code is below):

I do not believe you are required to pass in a new storage pool for 
each and every volume of the VM. If the VM has, say, three volumes, you may 
only try to migrate two of the volumes to new storage pools. This logic seems 
to assume if you want to migrate one of the VM’s volumes, then you necessarily 
want to migrate all of the VM’s volumes. I believe it’s possible for targetPool 
to come back null and later throw a NullPointerException. The old code walks 
through each volume of the VM and checks if there is a new storage pool 
specified for it. If so, do one thing; else, do something else.

private Map 
createMappingVolumeAndStoragePoolEnteredByUser(VirtualMachineProfile profile, 
Host host, Map volumeToPool) {
Map volumeToPoolObjectMap = new 
HashMap();
for(Long volumeId: volumeToPool.keySet()) {
VolumeVO volume = _volsDao.findById(volumeId);

Long poolId = volu

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Actually, I think I answered both of your questions with these two prior 
e-mails. Please let me know if you need further clarification. Thanks!

On 7/16/18, 2:17 PM, "Tutkowski, Mike"  wrote:

Allow me to correct what I said here:

“If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, we 
silently ignore the (faulty) input (which is a new storage pool) from the user 
and keep the volume in its same managed storage pool (the user may wonder why 
it wasn’t migrated if they don’t get an error message back telling them this is 
not allowed).”

I should have said the following:

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked on a VM 
that is using managed storage that is only at the cluster level (managed 
storage can be at either the zone or cluster level) and we are trying to 
migrate the VM from one cluster to another, this operation should fail (as the 
old code detects). The new code tries to keep the volume in the same storage 
pool (but that storage pool will not be visible to the hosts in the destination 
compute cluster).

On 7/16/18, 2:10 PM, "Tutkowski, Mike"  wrote:

Let me answer the questions in two separate e-mails.

This answer deals with what you wrote about this code:

> if (destPool.getId() == currentPool.getId()) {
> volumeToPoolObjectMap.put(volume, currentPool);
> } else {
>  throw new CloudRuntimeException("Currently, a volume on 
managed
> storage can only be 'migrated' to itself.");
> }
>

The code above is invoked if the user tries to migrate a volume that’s 
on managed storage to another storage pool. At present, such volumes can be 
migrated when a VM is migrated from one compute cluster to another, but those 
volumes have to remain on the same managed storage.

Here’s an example:

Let’s say VM_1 is in Cluster_1. VM_1 has a root (or data) disk on 
managed storage. We try to migrate the VM from Cluster_1 to Cluster_2 and 
specify a new storage pool for the volume. This case should fail. To make it 
work, you need to either 1) not specify a new storage pool or 2) specify the 
same storage pool the volume is already in. If the managed storage in question 
is zone wide, then it can be used from both Cluster_1 and Cluster_2.

The new code might call 
getDefaultMappingOfVolumesAndStoragePoolForMigration (if no storage pools at 
all are passed in to the API) or it might call 
createMappingVolumeAndStoragePoolEnteredByUser.

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, we 
silently ignore the (faulty) input (which is a new storage pool) from the user 
and keep the volume in its same managed storage pool (the user may wonder why 
it wasn’t migrated if they don’t get an error message back telling them this is 
not allowed).

If createMappingVolumeAndStoragePoolEnteredByUser is invoked, we seem 
to have a bigger problem (code is below):

I do not believe you are required to pass in a new storage pool for 
each and every volume of the VM. If the VM has, say, three volumes, you may 
only try to migrate two of the volumes to new storage pools. This logic seems 
to assume if you want to migrate one of the VM’s volumes, then you necessarily 
want to migrate all of the VM’s volumes. I believe it’s possible for targetPool 
to come back null and later throw a NullPointerException. The old code walks 
through each volume of the VM and checks if there is a new storage pool 
specified for it. If so, do one thing; else, do something else.

private Map 
createMappingVolumeAndStoragePoolEnteredByUser(VirtualMachineProfile profile, 
Host host, Map volumeToPool) {
Map volumeToPoolObjectMap = new 
HashMap();
for(Long volumeId: volumeToPool.keySet()) {
VolumeVO volume = _volsDao.findById(volumeId);

Long poolId = volumeToPool.get(volumeId);
StoragePoolVO targetPool = _storagePoolDao.findById(poolId);
StoragePoolVO currentPool = 
_storagePoolDao.findById(volume.getPoolId());

if (_poolHostDao.findByPoolHost(targetPool.getId(), 
host.getId()) == null) {
throw new CloudRuntimeException(String.format("Cannot 
migrate the volume [%s] to the storage pool [%s] while migrating VM [%s] to 
target host [%s]. The host does not have access to the storage pool entered.", 
volume.getUuid(), targetPool.getUuid(), profile.getUuid(), host.getUuid()));
}
if (currentPool.getId() == targetPool.getId()) {
s_logger.info(String.format("The volume [%s] is already 
allo

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Allow me to correct what I said here:

“If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, we 
silently ignore the (faulty) input (which is a new storage pool) from the user 
and keep the volume in its same managed storage pool (the user may wonder why 
it wasn’t migrated if they don’t get an error message back telling them this is 
not allowed).”

I should have said the following:

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked on a VM that 
is using managed storage that is only at the cluster level (managed storage can 
be at either the zone or cluster level) and we are trying to migrate the VM 
from one cluster to another, this operation should fail (as the old code 
detects). The new code tries to keep the volume in the same storage pool (but 
that storage pool will not be visible to the hosts in the destination compute 
cluster).

On 7/16/18, 2:10 PM, "Tutkowski, Mike"  wrote:

Let me answer the questions in two separate e-mails.

This answer deals with what you wrote about this code:

> if (destPool.getId() == currentPool.getId()) {
> volumeToPoolObjectMap.put(volume, currentPool);
> } else {
>  throw new CloudRuntimeException("Currently, a volume on managed
> storage can only be 'migrated' to itself.");
> }
>

The code above is invoked if the user tries to migrate a volume that’s on 
managed storage to another storage pool. At present, such volumes can be 
migrated when a VM is migrated from one compute cluster to another, but those 
volumes have to remain on the same managed storage.

Here’s an example:

Let’s say VM_1 is in Cluster_1. VM_1 has a root (or data) disk on managed 
storage. We try to migrate the VM from Cluster_1 to Cluster_2 and specify a new 
storage pool for the volume. This case should fail. To make it work, you need 
to either 1) not specify a new storage pool or 2) specify the same storage pool 
the volume is already in. If the managed storage in question is zone wide, then 
it can be used from both Cluster_1 and Cluster_2.

The new code might call 
getDefaultMappingOfVolumesAndStoragePoolForMigration (if no storage pools at 
all are passed in to the API) or it might call 
createMappingVolumeAndStoragePoolEnteredByUser.

If getDefaultMappingOfVolumesAndStoragePoolForMigration is invoked, we 
silently ignore the (faulty) input (which is a new storage pool) from the user 
and keep the volume in its same managed storage pool (the user may wonder why 
it wasn’t migrated if they don’t get an error message back telling them this is 
not allowed).

If createMappingVolumeAndStoragePoolEnteredByUser is invoked, we seem to 
have a bigger problem (code is below):

I do not believe you are required to pass in a new storage pool for each 
and every volume of the VM. If the VM has, say, three volumes, you may only try 
to migrate two of the volumes to new storage pools. This logic seems to assume 
if you want to migrate one of the VM’s volumes, then you necessarily want to 
migrate all of the VM’s volumes. I believe it’s possible for targetPool to come 
back null and later throw a NullPointerException. The old code walks through 
each volume of the VM and checks if there is a new storage pool specified for 
it. If so, do one thing; else, do something else.

private Map 
createMappingVolumeAndStoragePoolEnteredByUser(VirtualMachineProfile profile, 
Host host, Map volumeToPool) {
Map volumeToPoolObjectMap = new 
HashMap();
for(Long volumeId: volumeToPool.keySet()) {
VolumeVO volume = _volsDao.findById(volumeId);

Long poolId = volumeToPool.get(volumeId);
StoragePoolVO targetPool = _storagePoolDao.findById(poolId);
StoragePoolVO currentPool = 
_storagePoolDao.findById(volume.getPoolId());

if (_poolHostDao.findByPoolHost(targetPool.getId(), 
host.getId()) == null) {
throw new CloudRuntimeException(String.format("Cannot 
migrate the volume [%s] to the storage pool [%s] while migrating VM [%s] to 
target host [%s]. The host does not have access to the storage pool entered.", 
volume.getUuid(), targetPool.getUuid(), profile.getUuid(), host.getUuid()));
}
if (currentPool.getId() == targetPool.getId()) {
s_logger.info(String.format("The volume [%s] is already 
allocated in storage pool [%s].", volume.getUuid(), targetPool.getUuid()));
}
volumeToPoolObjectMap.put(volume, targetPool);
}
return volumeToPoolObjectMap;
}

On 7/16/18, 5:13 AM, "Rafael Weingärtner"  
wrote:

Ok, I see what happened there with the migration to cluster. When I 
re-did
the code I did not have this case.

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

ore starting to code. Thanks for spotting
this issue.

On Sun, Jul 15, 2018 at 9:11 PM, Tutkowski, Mike 
wrote:

> Hi Rafael,
>
> Thanks for your time on this.
>
> Here is an example where the new code deviates from the old code in a
> critical fashion (code right below is new):
>
> private Map getDefaultMappingOfVolumesAndS
> toragePoolForMigration(VirtualMachineProfile profile, Host targetHost) {
> Map volumeToPoolObjectMap = new
> HashMap();
> List allVolumes = _volsDao.findUsableVolumesForInstance(
> profile.getId());
> for (VolumeVO volume : allVolumes) {
> StoragePoolVO currentPool = _storagePoolDao.findById(
> volume.getPoolId());
> if (ScopeType.HOST.equals(currentPool.getScope())) {
> createVolumeToStoragePoolMappingIfNeeded(profile,
> targetHost, volumeToPoolObjectMap, volume, currentPool);
> } else {
> volumeToPoolObjectMap.put(volume, currentPool);
> }
> }
> return volumeToPoolObjectMap;
> }
>
> What happens in the new code (above) is if the user didn’t pass in a
> storage pool to migrate the virtual disk to (but the VM is being migrated
> to a new cluster), this code just assigns the virtual disk to its current
> storage pool (which is not going to be visible to any of the hosts in the
> new compute cluster).
>
> In the old code (I’m looking at 4.11.3 here), you could look around line
> 2337 for the following code (in the VirtualMachineManagerImpl.
> getPoolListForVolumesForMigration method):
>
> // Find a suitable pool for the volume. Call the
> storage pool allocator to find the list of pools.
>
> final DiskProfile diskProfile = new
> DiskProfile(volume, diskOffering, profile.getHypervisorType());
> final DataCenterDeployment plan = new
> DataCenterDeployment(host.getDataCenterId(), host.getPodId(),
> host.getClusterId(),
> host.getId(), null, null);
>
> final List poolList = new ArrayList<>();
> final ExcludeList avoid = new ExcludeList();
>
> for (final StoragePoolAllocator allocator :
> _storagePoolAllocators) {
> final List poolListFromAllocator =
> allocator.allocateToPool(diskProfile, profile, plan, avoid,
> StoragePoolAllocator.RETURN_UPTO_ALL);
>
> if (poolListFromAllocator != null &&
> !poolListFromAllocator.isEmpty()) {
> poolList.addAll(poolListFromAllocator);
> }
> }
>
> This old code would find an applicable storage pool in the destination
> cluster (one that can be seen by the hosts in that compute cluster).
>
> I think the main error in the new logic is the assumption that a VM can
> only be migrated to a host in the same computer cluster. For XenServer
> (perhaps for other hypervisor types?), we support cross-cluster VM
> migration.
>
> The other issue I noticed is that there is no logic in the new code that
> checks for managed-storage use cases. If you look in the
> VirtualMachineManagerImpl.getPoolListForVolumesForMigration method in the
> old code, there is special handling for managed storage. I don’t see this
> reproduced in the new logic.
>
> I sympathize with your point that all tests passed yet this issue was not
> uncovered. Unfortunately, I suspect we have a fairly low % coverage of
> automated tests on CloudStack. If we ever did get to a high % of automated
> test coverage, we might be able to spin up new releases more frequently. 
As
> the case stands today, however, there are probably many un-tested use 
cases
> when it comes to our automated suite of tests.
>
> Thanks again!
> Mike
>
> On 7/15/18, 4:19 PM, "Rafael Weingärtner" 
> wrote:
>
> Mike, are you able to pin-point in the old/replaced code the bit that
> was
> handling your use case?  I took the most care not to break anything.
> Also, your test case, isn't it in the ACS' integration test suite? In
> theory, all test passed when we merged the PR.
>
> I sure can take a look at it. Can you detail your use case? I mean, 
the
> high level execution flow. What API methods you

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

I should be able to do so soon. I’ve been in meetings all day. I’ll try to 
investigate this before my next meeting starts.

On 7/16/18, 1:45 PM, "Rafael Weingärtner"  wrote:

Yes, that is what happened. I also followed this principle. That is why I
create the PR against master, but I think people are not following this.

Mike, can you provide me some feedback regarding those two inquiries? Then,
we can fix this quickly.

On Mon, Jul 16, 2018 at 4:42 PM, Tutkowski, Mike 
wrote:

> OK, as Rafael noted, looks like it’s in 4.11.2. My regression tests were
> run against 4.11.1. I thought we only allowed bug fixes when going to a 
new
> RC, but it appears we are not strictly enforcing that rule.
>
> On 7/16/18, 1:40 PM, "Tutkowski, Mike"  wrote:
>
> When I ran my suite of tests on 4.11.1, I did not encounter this
> issue. Also, looking at the code now, it appears this new code is first in
> 4.12.
>
> On 7/16/18, 1:36 PM, "Yiping Zhang"  wrote:
>
>
> Is this code already in ACS 4.11.1.0?
>
> CLOUDSTACK-10240 is listed as fixed in 4.11.1.0, according to
> release note here, http://docs.cloudstack.apache.org/projects/cloudstack-
> release-notes/ja/master/fixed_issues.html, but in the JIRA ticket itself,
> the "fixed version/s" field says 4.12.
>
> We are using XenServer clusters with shared NFS storages and I am
> about to migrate to ACS 4.11.1.0 from 4.9.3.0.  Since we move VM between
> clusters a lot, this is going to be a blocker for us.  Someone please
> confirm.
    >
> Thanks
>
> Yiping
>
>
> On 7/14/18, 11:20 PM, "Tutkowski, Mike" 

> wrote:
>
> Hi,
>
> While running managed-storage regression tests tonight, I
> noticed a problem that is not related to managed storage.
>
> CLOUDSTACK-10240 is a ticket asking that we allow the
> migration of a virtual disk that’s on local storage to shared storage. In
> the process of enabling this feature, the VirtualMachineManagerImpl.
> getPoolListForVolumesForMigration method was re-written in a way that
> completely breaks at least one use case: Migrating a VM across compute
> clusters (at least supported in XenServer). If, say, a virtual disk 
resides
> on shared storage in the source compute cluster, we must be able to copy
> this virtual disk to shared storage in the destination compute cluster.
>
> As the code is currently written, this is no longer possible.
> It also seems that the managed-storage logic has been dropped for some
> reason in the new implementation.
>
> Rafael – It seems that you worked on this feature. Would you
> be able to look into this and create a PR?
>
> Thanks,
> Mike
>
>
>
>
>
>
>


-- 
Rafael Weingärtner

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

OK, as Rafael noted, looks like it’s in 4.11.2. My regression tests were run 
against 4.11.1. I thought we only allowed bug fixes when going to a new RC, but 
it appears we are not strictly enforcing that rule.

On 7/16/18, 1:40 PM, "Tutkowski, Mike"  wrote:

When I ran my suite of tests on 4.11.1, I did not encounter this issue. 
Also, looking at the code now, it appears this new code is first in 4.12.

On 7/16/18, 1:36 PM, "Yiping Zhang"  wrote:


Is this code already in ACS 4.11.1.0? 

CLOUDSTACK-10240 is listed as fixed in 4.11.1.0, according to release 
note here, 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/ja/master/fixed_issues.html,
 but in the JIRA ticket itself, the "fixed version/s" field says 4.12.

We are using XenServer clusters with shared NFS storages and I am about 
to migrate to ACS 4.11.1.0 from 4.9.3.0.  Since we move VM between clusters a 
lot, this is going to be a blocker for us.  Someone please confirm.

Thanks

Yiping


    On 7/14/18, 11:20 PM, "Tutkowski, Mike"  
wrote:

Hi,

While running managed-storage regression tests tonight, I noticed a 
problem that is not related to managed storage.

CLOUDSTACK-10240 is a ticket asking that we allow the migration of 
a virtual disk that’s on local storage to shared storage. In the process of 
enabling this feature, the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method was 
re-written in a way that completely breaks at least one use case: Migrating a 
VM across compute clusters (at least supported in XenServer). If, say, a 
virtual disk resides on shared storage in the source compute cluster, we must 
be able to copy this virtual disk to shared storage in the destination compute 
cluster.

As the code is currently written, this is no longer possible. It 
also seems that the managed-storage logic has been dropped for some reason in 
the new implementation.

Rafael – It seems that you worked on this feature. Would you be 
able to look into this and create a PR?

Thanks,
Mike

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

When I ran my suite of tests on 4.11.1, I did not encounter this issue. Also, 
looking at the code now, it appears this new code is first in 4.12.

On 7/16/18, 1:36 PM, "Yiping Zhang"  wrote:


Is this code already in ACS 4.11.1.0? 

CLOUDSTACK-10240 is listed as fixed in 4.11.1.0, according to release note 
here, 
http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/ja/master/fixed_issues.html,
 but in the JIRA ticket itself, the "fixed version/s" field says 4.12.

We are using XenServer clusters with shared NFS storages and I am about to 
migrate to ACS 4.11.1.0 from 4.9.3.0.  Since we move VM between clusters a lot, 
this is going to be a blocker for us.  Someone please confirm.

Thanks

Yiping


On 7/14/18, 11:20 PM, "Tutkowski, Mike"  wrote:

Hi,

While running managed-storage regression tests tonight, I noticed a 
problem that is not related to managed storage.

CLOUDSTACK-10240 is a ticket asking that we allow the migration of a 
virtual disk that’s on local storage to shared storage. In the process of 
enabling this feature, the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method was 
re-written in a way that completely breaks at least one use case: Migrating a 
VM across compute clusters (at least supported in XenServer). If, say, a 
virtual disk resides on shared storage in the source compute cluster, we must 
be able to copy this virtual disk to shared storage in the destination compute 
cluster.

As the code is currently written, this is no longer possible. It also 
seems that the managed-storage logic has been dropped for some reason in the 
new implementation.

Rafael – It seems that you worked on this feature. Would you be able to 
look into this and create a PR?

Thanks,
Mike

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Hi Rafael,

Thanks for your time on this.

Here is an example where the new code deviates from the old code in a critical 
fashion (code right below is new):

private Map 
getDefaultMappingOfVolumesAndStoragePoolForMigration(VirtualMachineProfile 
profile, Host targetHost) {
Map volumeToPoolObjectMap = new HashMap();
List allVolumes = 
_volsDao.findUsableVolumesForInstance(profile.getId());
for (VolumeVO volume : allVolumes) {
StoragePoolVO currentPool = 
_storagePoolDao.findById(volume.getPoolId());
if (ScopeType.HOST.equals(currentPool.getScope())) {
createVolumeToStoragePoolMappingIfNeeded(profile, targetHost, 
volumeToPoolObjectMap, volume, currentPool);
} else {
volumeToPoolObjectMap.put(volume, currentPool);
}
}
return volumeToPoolObjectMap;
}

What happens in the new code (above) is if the user didn’t pass in a storage 
pool to migrate the virtual disk to (but the VM is being migrated to a new 
cluster), this code just assigns the virtual disk to its current storage pool 
(which is not going to be visible to any of the hosts in the new compute 
cluster).

In the old code (I’m looking at 4.11.3 here), you could look around line 2337 
for the following code (in the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method):

// Find a suitable pool for the volume. Call the storage 
pool allocator to find the list of pools.

final DiskProfile diskProfile = new DiskProfile(volume, 
diskOffering, profile.getHypervisorType());
final DataCenterDeployment plan = new 
DataCenterDeployment(host.getDataCenterId(), host.getPodId(), 
host.getClusterId(),
host.getId(), null, null);

final List poolList = new ArrayList<>();
final ExcludeList avoid = new ExcludeList();

for (final StoragePoolAllocator allocator : 
_storagePoolAllocators) {
final List poolListFromAllocator = 
allocator.allocateToPool(diskProfile, profile, plan, avoid, 
StoragePoolAllocator.RETURN_UPTO_ALL);

if (poolListFromAllocator != null && 
!poolListFromAllocator.isEmpty()) {
poolList.addAll(poolListFromAllocator);
}
}

This old code would find an applicable storage pool in the destination cluster 
(one that can be seen by the hosts in that compute cluster).

I think the main error in the new logic is the assumption that a VM can only be 
migrated to a host in the same computer cluster. For XenServer (perhaps for 
other hypervisor types?), we support cross-cluster VM migration.

The other issue I noticed is that there is no logic in the new code that checks 
for managed-storage use cases. If you look in the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method in the old 
code, there is special handling for managed storage. I don’t see this 
reproduced in the new logic.

I sympathize with your point that all tests passed yet this issue was not 
uncovered. Unfortunately, I suspect we have a fairly low % coverage of 
automated tests on CloudStack. If we ever did get to a high % of automated test 
coverage, we might be able to spin up new releases more frequently. As the case 
stands today, however, there are probably many un-tested use cases when it 
comes to our automated suite of tests.

Thanks again!
Mike

On 7/15/18, 4:19 PM, "Rafael Weingärtner"  wrote:

Mike, are you able to pin-point in the old/replaced code the bit that was
handling your use case?  I took the most care not to break anything.
Also, your test case, isn't it in the ACS' integration test suite? In
theory, all test passed when we merged the PR.

I sure can take a look at it. Can you detail your use case? I mean, the
high level execution flow. What API methods you do, what you expected to
happen, and what is happening today.

On Sun, Jul 15, 2018 at 3:25 AM, Tutkowski, Mike 
wrote:

> It looks like this is the problematic PR:
>
> https://github.com/apache/cloudstack/pull/2425/
    >
    > On 7/15/18, 12:20 AM, "Tutkowski, Mike"  wrote:
>
> Hi,
>
> While running managed-storage regression tests tonight, I noticed a
> problem that is not related to managed storage.
>
> CLOUDSTACK-10240 is a ticket asking that we allow the migration of a
> virtual disk that’s on local storage to shared storage. In the process of
> enabling this feature, the VirtualMachineManagerImpl.
> getPoolListForVolumesForMigration method was re-written in a way that
> completely breaks at least one use case: Migrating a VM across compute
> clusters (at least supported in XenServer). If, say, a

Re: Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

It looks like this is the problematic PR:

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

On 7/15/18, 12:20 AM, "Tutkowski, Mike"  wrote:

Hi,

While running managed-storage regression tests tonight, I noticed a problem 
that is not related to managed storage.

CLOUDSTACK-10240 is a ticket asking that we allow the migration of a 
virtual disk that’s on local storage to shared storage. In the process of 
enabling this feature, the 
VirtualMachineManagerImpl.getPoolListForVolumesForMigration method was 
re-written in a way that completely breaks at least one use case: Migrating a 
VM across compute clusters (at least supported in XenServer). If, say, a 
virtual disk resides on shared storage in the source compute cluster, we must 
be able to copy this virtual disk to shared storage in the destination compute 
cluster.

As the code is currently written, this is no longer possible. It also seems 
that the managed-storage logic has been dropped for some reason in the new 
implementation.

Rafael – It seems that you worked on this feature. Would you be able to 
look into this and create a PR?

Thanks,
Mike

Problem with CLOUDSTACK-10240 (Cannot migrate local volume to shared storage)

[Tutkowski, Mike]

Hi,

While running managed-storage regression tests tonight, I noticed a problem 
that is not related to managed storage.

CLOUDSTACK-10240 is a ticket asking that we allow the migration of a virtual 
disk that’s on local storage to shared storage. In the process of enabling this 
feature, the VirtualMachineManagerImpl.getPoolListForVolumesForMigration method 
was re-written in a way that completely breaks at least one use case: Migrating 
a VM across compute clusters (at least supported in XenServer). If, say, a 
virtual disk resides on shared storage in the source compute cluster, we must 
be able to copy this virtual disk to shared storage in the destination compute 
cluster.

As the code is currently written, this is no longer possible. It also seems 
that the managed-storage logic has been dropped for some reason in the new 
implementation.

Rafael – It seems that you worked on this feature. Would you be able to look 
into this and create a PR?

Thanks,
Mike

Re: GUI Issue

[Tutkowski, Mike]

Thanks, Bobby!

> On Jul 11, 2018, at 11:55 PM, Boris Stoyanov  
> wrote:
> 
> I’ve just checked and it does not work with me as well. Doesn’t look browser 
> related, tried it on both chrome and FF and still not working. Let me log an 
> issue about it. 
> 
> Bobby.
> 
> 
> boris.stoya...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> 
> 
>> On 11 Jul 2018, at 22:28, Tutkowski, Mike  wrote:
>> 
>> Hi,
>> 
>> Has anyone else noticed that you can no longer use the Quickview column to 
>> manipulate (i.e. delete, in this case) Disk Offerings in the GUI in master? 
>> The Quickview menu doesn’t show up. It works fine for Compute Offerings 
>> still, though.
>> 
>> Thanks,
>> Mike
> 

GUI Issue

[Tutkowski, Mike]

Hi,

Has anyone else noticed that you can no longer use the Quickview column to 
manipulate (i.e. delete, in this case) Disk Offerings in the GUI in master? The 
Quickview menu doesn’t show up. It works fine for Compute Offerings still, 
though.

Thanks,
Mike

Re: Open Summit CFP anyone ?

[Tutkowski, Mike]

Excellent 

> On Jun 26, 2018, at 5:51 PM, Andrija Panic  wrote:
> 
> Submitted...
> 
>> On Tue, 26 Jun 2018 at 21:12, Andrija Panic  wrote:
>> 
>> So, as discussed with Mike... I will submit similar thing as in Berlin,
>> just about running KVM with ACS (and SF) all opensource etc...
>> 
>> Giles, perhaps it would be good to make sure I don't overlap with Dan's
>> talk, not sure how much he will dive into KVM options/path with ACS...
>> 
>> Thx
>> 
>>> On Tue, Jun 26, 2018, 20:41 Andrija Panic  wrote:
>>> 
>>> That is OK from my side, but they insist on open source (acs is...) but
>>> not sure about SF, at least what I read on CFP page...could you give it a
>>> read ?
>>> 
>>> Otherwise I'm perfectly fine!
>>> 
>>> On Tue, Jun 26, 2018, 18:34 Tutkowski, Mike 
>>> wrote:
>>> 
>>>> You could submit the talk you just did in Berlin. It’s a different
>>>> conference in a different location, so I think doing the same presentation
>>>> is perfectly fine.
>>>> 
>>>>> On Jun 26, 2018, at 4:50 AM, Andrija Panic 
>>>> wrote:
>>>>> 
>>>>> I would love to, yes, just don't have concrete idea atm...?
>>>>> 
>>>>>> On Tue, Jun 26, 2018, 11:58 Giles Sirett 
>>>> wrote:
>>>>>> 
>>>>>> I know Dag (in CC) has submitted a "Intro to cloudstack" talk -  but
>>>> he's
>>>>>> away on holiday at the moment
>>>>>> 
>>>>>> Andrija - are you still planning on submitting something ?
>>>>>> 
>>>>>> Kind regards
>>>>>> Giles
>>>>>> 
>>>>>> giles.sir...@shapeblue.com
>>>>>> www.shapeblue.com
>>>>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>>>>>> @shapeblue
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -Original Message-
>>>>>> From: Stephan Seitz 
>>>>>> Sent: 21 June 2018 16:54
>>>>>> To: dev@cloudstack.apache.org
>>>>>> Subject: Re: Open Summit CFP anyone ?
>>>>>> 
>>>>>> Hey!
>>>>>> 
>>>>>> I'm also interested :) Actually planning a talk abount attaching
>>>>>> active/active iSCSI targets w/ TCQ and ALUA capability to a ceph
>>>> cluster.
>>>>>> 
>>>>>> Am Donnerstag, den 21.06.2018, 15:43 + schrieb Tutkowski, Mike:
>>>>>>> I am interested.
>>>>>>> 
>>>>>>>> 
>>>>>>>> On Jun 21, 2018, at 2:38 AM, Giles Sirett <
>>>> giles.sir...@shapeblue.com>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Hi Andrija
>>>>>>>> - yes I think it would be a great idea for Cloudstack to have some
>>>>>> talks there.
>>>>>>>> 
>>>>>>>> Open source summit appears to be Linux Foundations replacement for
>>>>>>>> Linuxcon/cloudopen - people from this community have spoken at these
>>>>>>>> before and had good attendance
>>>>>>>> 
>>>>>>>> Lets coordinate on here some submissions.
>>>>>>>> 
>>>>>>>> First of all, anybody else fancy submitting for this ?
>>>>>>>> 
>>>>>>>> Kind regards
>>>>>>>> Giles
>>>>>>>> 
>>>>>>>> giles.sir...@shapeblue.com
>>>>>>>> www.shapeblue.com
>>>>>>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> -Original Message-
>>>>>>>> From: Andrija Panic 
>>>>>>>> Sent: 20 June 2018 21:52
>>>>>>>> To: dev 
>>>>>>>> Subject: Open Summit CFP anyone ?
>>>>>>>> 
>>>>>>>> Hi all,
>>>>>>>> 
>>>>>>>> Just wondering if anyone submitted CFP here:
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>> https://events.linuxfoundation.org/events/open-source-summit-europe-2018/program/cfp/
>>>>>>>> 
>>>>>>>> Sounds like an interesting place to present the products (ACS) - if
>>>>>> anyone interested, I'm happy to share the work(load) and present
>>>> jointly,
>>>>>> or similar...
>>>>>>>> 
>>>>>>>> Deadline for CFP is 1st July...
>>>>>>>> 
>>>>>>>> Anyone?
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> Andrija
>>>>>> Mit freundlichen Grüßen,
>>>>>> 
>>>>>> Stephan Seitz
>>>>>> 
>>>>>> --
>>>>>> 
>>>>>> Heinlein Support GmbH
>>>>>> Schwedter Str. 8/9b, 10119 Berlin
>>>>>> 
>>>>>> http://www.heinlein-support.de
>>>>>> 
>>>>>> Tel: 030 / 405051-44
>>>>>> Fax: 030 / 405051-19
>>>>>> 
>>>>>> Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht
>>>>>> Berlin-Charlottenburg,
>>>>>> Geschäftsführer: Peer Heinlein -- Sitz: Berlin
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>> 
> 
> -- 
> 
> Andrija Panić

Re: Open Summit CFP anyone ?

[Tutkowski, Mike]

You could submit the talk you just did in Berlin. It’s a different conference 
in a different location, so I think doing the same presentation is perfectly 
fine.

> On Jun 26, 2018, at 4:50 AM, Andrija Panic  wrote:
> 
> I would love to, yes, just don't have concrete idea atm...?
> 
>> On Tue, Jun 26, 2018, 11:58 Giles Sirett  wrote:
>> 
>> I know Dag (in CC) has submitted a "Intro to cloudstack" talk -  but he's
>> away on holiday at the moment
>> 
>> Andrija - are you still planning on submitting something ?
>> 
>> Kind regards
>> Giles
>> 
>> giles.sir...@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> @shapeblue
>> 
>> 
>> 
>> 
>> -Original Message-
>> From: Stephan Seitz 
>> Sent: 21 June 2018 16:54
>> To: dev@cloudstack.apache.org
>> Subject: Re: Open Summit CFP anyone ?
>> 
>> Hey!
>> 
>> I'm also interested :) Actually planning a talk abount attaching
>> active/active iSCSI targets w/ TCQ and ALUA capability to a ceph cluster.
>> 
>> Am Donnerstag, den 21.06.2018, 15:43 + schrieb Tutkowski, Mike:
>>> I am interested.
>>> 
>>>> 
>>>> On Jun 21, 2018, at 2:38 AM, Giles Sirett 
>> wrote:
>>>> 
>>>> Hi Andrija
>>>> - yes I think it would be a great idea for Cloudstack to have some
>> talks there.
>>>> 
>>>> Open source summit appears to be Linux Foundations replacement for
>>>> Linuxcon/cloudopen - people from this community have spoken at these
>>>> before and had good attendance
>>>> 
>>>> Lets coordinate on here some submissions.
>>>> 
>>>> First of all, anybody else fancy submitting for this ?
>>>> 
>>>> Kind regards
>>>> Giles
>>>> 
>>>> giles.sir...@shapeblue.com
>>>> www.shapeblue.com
>>>> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -Original Message-
>>>> From: Andrija Panic 
>>>> Sent: 20 June 2018 21:52
>>>> To: dev 
>>>> Subject: Open Summit CFP anyone ?
>>>> 
>>>> Hi all,
>>>> 
>>>> Just wondering if anyone submitted CFP here:
>>>> 
>>>> 
>> https://events.linuxfoundation.org/events/open-source-summit-europe-2018/program/cfp/
>>>> 
>>>> Sounds like an interesting place to present the products (ACS) - if
>> anyone interested, I'm happy to share the work(load) and present jointly,
>> or similar...
>>>> 
>>>> Deadline for CFP is 1st July...
>>>> 
>>>> Anyone?
>>>> 
>>>> Cheers,
>>>> Andrija
>> Mit freundlichen Grüßen,
>> 
>> Stephan Seitz
>> 
>> --
>> 
>> Heinlein Support GmbH
>> Schwedter Str. 8/9b, 10119 Berlin
>> 
>> http://www.heinlein-support.de
>> 
>> Tel: 030 / 405051-44
>> Fax: 030 / 405051-19
>> 
>> Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht
>> Berlin-Charlottenburg,
>> Geschäftsführer: Peer Heinlein -- Sitz: Berlin
>> 
>> 
>> 
>> 

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC3]

[Tutkowski, Mike]

+1 (binding) (Based on my testing of RC1 and not seeing anything that concerned 
me going into RC2 or RC3.)

On 6/21/18, 9:59 AM, "Paul Angus"  wrote:

Hi All,



I've created a 4.11.1.0 release (RC3), with the following artefacts up for 
testing and a vote:
The changes since RC2 are listed at the end of this email.



Git Branch and Commit SH:


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

Commit: 2cb2dacbe75a23f5068b80f6ea45031c29052c31



Source release (checksums and signatures are available at the same

location):

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



PGP release keys (signed using 8B309F7251EE0BC8):

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



The vote will be open for at least 72hrs.



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 
5f48487dc62fd1decaabc4ab2a10f549d6c82400 and published RC1 repository here:

http://packages.shapeblue.com/testing/4111rc3/



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.1 systemvm templates are available from here:

http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/




Changes Since RC2:

Merged #2712 reuse ip for non redundant VPC 6 hours ago
Merged #2714 send unsupported answer only when applicable 10 hours ago
Merged #2715 smoketest: Fix test_vm_life_cycle secure migration tests a day 
ago
Merged #2493 CLOUDSTACK-10326: Prevent hosts fall into Maintenance when 
there are running VMs on it a day ago
Merged #2716 configdrive: make fewer mountpoints on hosts a day ago
Merged #2681 Source NAT option on Private Gateway 2 days ago
Merged #2710 comply with api key constraint 2 days ago
Merged #2706 packaging: use libuuid x86_64 package for cloudstack-common 2 
days ago

Kind regards,

Paul Angus


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

Re: Open Summit CFP anyone ?

[Tutkowski, Mike]

I am interested.

> On Jun 21, 2018, at 2:38 AM, Giles Sirett  wrote:
> 
> Hi Andrija
> - yes I think it would be a great idea for Cloudstack to have some talks 
> there.
> 
> Open source summit appears to be Linux Foundations replacement for 
> Linuxcon/cloudopen - people from this community have spoken at these before 
> and had good attendance
> 
> Lets coordinate on here some submissions.
> 
> First of all, anybody else fancy submitting for this ?
> 
> Kind regards
> Giles
> 
> giles.sir...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> 
> 
> 
> -Original Message-
> From: Andrija Panic  
> Sent: 20 June 2018 21:52
> To: dev 
> Subject: Open Summit CFP anyone ?
> 
> Hi all,
> 
> Just wondering if anyone submitted CFP here:
> 
> https://events.linuxfoundation.org/events/open-source-summit-europe-2018/program/cfp/
> 
> Sounds like an interesting place to present the products (ACS) - if anyone 
> interested, I'm happy to share the work(load) and present jointly, or 
> similar...
> 
> Deadline for CFP is 1st July...
> 
> Anyone?
> 
> Cheers,
> Andrija

Re: [DISCUSS] Blocking the creation of new Basic Networking zones

[Tutkowski, Mike]

Also, yes, I agree with the list you provided, Wido. We might have to break 
“other fancy stuff” into more detail, though. ;)

On 6/20/18, 12:32 PM, "Tutkowski, Mike"  wrote:

Sorry, Wido :) I missed that part.

On 6/20/18, 5:03 AM, "Wido den Hollander"  wrote:



On 06/20/2018 12:31 AM, Tutkowski, Mike wrote:
> If this initiative goes through, perhaps that’s a good time to bump 
CloudStack’s release number to 5.0.0?
> 

That's what I said in my e-mail :-) But yes, I agree with you, this
might be a good time to bump it to 5.0

With that we would:

- Drop creation of new Basic Networking Zones
- Support IPv6 in shared IPv6 networks
- Java 9?
- Drop support for Ubuntu 12.04
- Other fancy stuff?
- Support ConfigDrive in all scenarios properly

How would that sound?

Wido

>> On Jun 19, 2018, at 3:17 PM, Wido den Hollander  
wrote:
>>
>>
>>
>>> On 06/19/2018 11:07 PM, Daan Hoogland wrote:
>>> I like this initiative, and here comes the big but even though I 
myself
>>> might think it is not valid; Basic zones are there to give a simple 
start
>>> for new users. If we can give a one-knob start/one page wizard for 
creating
>>> a shared network in advanced zone with security groups and 
userdata, great.
>>
>> That would be a UI thing, but it would be a matter of using VLAN
>> isolation and giving in VLAN 0 or 'untagged', because that's 
basically
>> what Basic Networking does.
>>
>> It plugs the VM on top of usually cloudbr0 (KVM).
>>
>> If you use vlan://untagged for the broadcast_uri in Advanced 
Networking
>> you get exactly the same result.
>>
>>> And I really fancy this idea. let's make ACS more simple by 
throwing at as
>>> much code as we can in a gradual and controlled way :+1:
>>
>> I would love to. But I'm a real novice when it comes to the UI 
though.
>> So that would be something I wouldn't be good at doing.
>>
>> Blocking Basic Networking creation is a few if-statements at the 
right
>> location and you're done.
>>
>> Wido
>>
>>>
>>>> On Tue, Jun 19, 2018 at 10:57 PM, Wido den Hollander 
 wrote:
>>>>
>>>> Hi,
>>>>
>>>> We (PCextreme) are a big-time user of Basic Networking and recently
>>>> started to look into Advanced Networking with VLAN isolation and a
>>>> shared network.
>>>>
>>>> This provides (from what we can see) all the features Basic 
Networking
>>>> provides, like the VR just doing DHCP and UserData while the 
Hypervisor
>>>> does the Security Grouping.
>>>>
>>>> That made me wonder why we still have Basic Networking.
>>>>
>>>> Dropping all the code would be a big problem for users as you can't
>>>> simply migrate from Basic to Advanced. In theory we found out that 
it's
>>>> possible by changing the database, but I wouldn't guarantee it 
works in
>>>> every use-case. So doing this automatically during a upgrade would 
be
>>>> difficult.
>>>>
>>>> To prevent us from having to maintain the Basic Networking code 
for ever
>>>> I would like to propose and discuss the matter of preventing the
>>>> creation of new Basic Networking zones.
>>>>
>>>> In the future this can get us rid of a lot of if-else statements 
in the
>>>> code and it would make testing also easier as we have few things 
to test.
>>>>
>>>> Most of the development also seems to go in the Advanced Networking
>>>> direction.
>>>>
>>>> We are currently also working on IPv6 in Advanced Shared Networks 
and
>>>> that's progressing very good as well.
>>>>
>>>> Would this be something to call the 5.0 release where we simplify 
the
>>>> networking and in the UI/API get rid of Basic Networking while 
keeping
>>>> it alive for existing users?
>>>>
>>>> Wido
>>>>
>>>
>>>
>>>

Re: [DISCUSS] Blocking the creation of new Basic Networking zones

[Tutkowski, Mike]

Sorry, Wido :) I missed that part.

On 6/20/18, 5:03 AM, "Wido den Hollander"  wrote:



On 06/20/2018 12:31 AM, Tutkowski, Mike wrote:
> If this initiative goes through, perhaps that’s a good time to bump 
CloudStack’s release number to 5.0.0?
> 

That's what I said in my e-mail :-) But yes, I agree with you, this
might be a good time to bump it to 5.0

With that we would:

- Drop creation of new Basic Networking Zones
- Support IPv6 in shared IPv6 networks
- Java 9?
- Drop support for Ubuntu 12.04
- Other fancy stuff?
- Support ConfigDrive in all scenarios properly

How would that sound?

Wido

>> On Jun 19, 2018, at 3:17 PM, Wido den Hollander  wrote:
>>
>>
>>
>>> On 06/19/2018 11:07 PM, Daan Hoogland wrote:
>>> I like this initiative, and here comes the big but even though I myself
>>> might think it is not valid; Basic zones are there to give a simple 
start
>>> for new users. If we can give a one-knob start/one page wizard for 
creating
>>> a shared network in advanced zone with security groups and userdata, 
great.
>>
>> That would be a UI thing, but it would be a matter of using VLAN
>> isolation and giving in VLAN 0 or 'untagged', because that's basically
>> what Basic Networking does.
>>
>> It plugs the VM on top of usually cloudbr0 (KVM).
>>
>> If you use vlan://untagged for the broadcast_uri in Advanced Networking
>> you get exactly the same result.
>>
>>> And I really fancy this idea. let's make ACS more simple by throwing at 
as
>>> much code as we can in a gradual and controlled way :+1:
>>
>> I would love to. But I'm a real novice when it comes to the UI though.
>> So that would be something I wouldn't be good at doing.
>>
>> Blocking Basic Networking creation is a few if-statements at the right
>> location and you're done.
>>
>> Wido
>>
>>>
>>>> On Tue, Jun 19, 2018 at 10:57 PM, Wido den Hollander  
wrote:
>>>>
>>>> Hi,
>>>>
>>>> We (PCextreme) are a big-time user of Basic Networking and recently
>>>> started to look into Advanced Networking with VLAN isolation and a
>>>> shared network.
>>>>
>>>> This provides (from what we can see) all the features Basic Networking
>>>> provides, like the VR just doing DHCP and UserData while the Hypervisor
>>>> does the Security Grouping.
>>>>
>>>> That made me wonder why we still have Basic Networking.
>>>>
>>>> Dropping all the code would be a big problem for users as you can't
>>>> simply migrate from Basic to Advanced. In theory we found out that it's
>>>> possible by changing the database, but I wouldn't guarantee it works in
>>>> every use-case. So doing this automatically during a upgrade would be
>>>> difficult.
>>>>
>>>> To prevent us from having to maintain the Basic Networking code for 
ever
>>>> I would like to propose and discuss the matter of preventing the
>>>> creation of new Basic Networking zones.
>>>>
>>>> In the future this can get us rid of a lot of if-else statements in the
>>>> code and it would make testing also easier as we have few things to 
test.
>>>>
>>>> Most of the development also seems to go in the Advanced Networking
>>>> direction.
>>>>
>>>> We are currently also working on IPv6 in Advanced Shared Networks and
>>>> that's progressing very good as well.
>>>>
>>>> Would this be something to call the 5.0 release where we simplify the
>>>> networking and in the UI/API get rid of Basic Networking while keeping
>>>> it alive for existing users?
>>>>
>>>> Wido
>>>>
>>>
>>>
>>>

Re: [DISCUSS] Blocking the creation of new Basic Networking zones

[Tutkowski, Mike]

If this initiative goes through, perhaps that’s a good time to bump 
CloudStack’s release number to 5.0.0?

> On Jun 19, 2018, at 3:17 PM, Wido den Hollander  wrote:
> 
> 
> 
>> On 06/19/2018 11:07 PM, Daan Hoogland wrote:
>> I like this initiative, and here comes the big but even though I myself
>> might think it is not valid; Basic zones are there to give a simple start
>> for new users. If we can give a one-knob start/one page wizard for creating
>> a shared network in advanced zone with security groups and userdata, great.
> 
> That would be a UI thing, but it would be a matter of using VLAN
> isolation and giving in VLAN 0 or 'untagged', because that's basically
> what Basic Networking does.
> 
> It plugs the VM on top of usually cloudbr0 (KVM).
> 
> If you use vlan://untagged for the broadcast_uri in Advanced Networking
> you get exactly the same result.
> 
>> And I really fancy this idea. let's make ACS more simple by throwing at as
>> much code as we can in a gradual and controlled way :+1:
> 
> I would love to. But I'm a real novice when it comes to the UI though.
> So that would be something I wouldn't be good at doing.
> 
> Blocking Basic Networking creation is a few if-statements at the right
> location and you're done.
> 
> Wido
> 
>> 
>>> On Tue, Jun 19, 2018 at 10:57 PM, Wido den Hollander  wrote:
>>> 
>>> Hi,
>>> 
>>> We (PCextreme) are a big-time user of Basic Networking and recently
>>> started to look into Advanced Networking with VLAN isolation and a
>>> shared network.
>>> 
>>> This provides (from what we can see) all the features Basic Networking
>>> provides, like the VR just doing DHCP and UserData while the Hypervisor
>>> does the Security Grouping.
>>> 
>>> That made me wonder why we still have Basic Networking.
>>> 
>>> Dropping all the code would be a big problem for users as you can't
>>> simply migrate from Basic to Advanced. In theory we found out that it's
>>> possible by changing the database, but I wouldn't guarantee it works in
>>> every use-case. So doing this automatically during a upgrade would be
>>> difficult.
>>> 
>>> To prevent us from having to maintain the Basic Networking code for ever
>>> I would like to propose and discuss the matter of preventing the
>>> creation of new Basic Networking zones.
>>> 
>>> In the future this can get us rid of a lot of if-else statements in the
>>> code and it would make testing also easier as we have few things to test.
>>> 
>>> Most of the development also seems to go in the Advanced Networking
>>> direction.
>>> 
>>> We are currently also working on IPv6 in Advanced Shared Networks and
>>> that's progressing very good as well.
>>> 
>>> Would this be something to call the 5.0 release where we simplify the
>>> networking and in the UI/API get rid of Basic Networking while keeping
>>> it alive for existing users?
>>> 
>>> Wido
>>> 
>> 
>> 
>> 

Re: PR 2670: Removing an old, unused NetApp plug-in

[Tutkowski, Mike]

Just an FYI that I merged this PR into master today.

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

On 5/24/18, 1:41 AM, "Rohit Yadav"  wrote:

+1 on removal of unused plugin including removal of related files, db 
tables and any global settings.


- Rohit

<https://cloudstack.apache.org>



____
    From: Tutkowski, Mike 
Sent: Thursday, May 24, 2018 1:06:52 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
Subject: Re: PR 2670: Removing an old, unused NetApp plug-in

Including users@ on this (below).


rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

On May 23, 2018, at 12:53 PM, Tutkowski, Mike 
mailto:mike.tutkow...@netapp.com>> wrote:

Hi everyone,

I opened the following PR today:

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

There is an old, what we believe to be unused, NetApp plug-in in the 
CloudStack codebase that I’d like to remove.

I’m sending this e-mail out for the following reasons:


1)   To see if, by chance, anyone is actually using this plug-in.

2)   To direct any potential code reviewers to this PR, where I have 
placed a couple questions about my commit.

To be absolutely clear here, this has nothing to do with any of the 
SolidFire plug-ins (only an old NetApp plug-in that hasn’t been updated in 
years and is probably not being used by anyone).

Thanks,
Mike

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC2]

[Tutkowski, Mike]

+1 (binding)

This is what I did for RC1:

I created a new cloud using commit 5f48487dc62fd1decaabc4ab2a10f549d6c82400 
(RC1). I ran the automated regression tests for managed storage. All tests 
passed.

This is what I did for RC2:

I looked at the Git changelog and didn’t see anything that seemed like it would 
impact the prior success of my testing for RC1.

On 6/11/18, 9:49 AM, "Paul Angus"  wrote:

Hi All,



I've created a 4.11.1.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.1.0-RC20180611T1504

Commit: bcf602c7cd4ab662a7c4f208dee32fb8513e26c8



Source release (checksums and signatures are available at the same

location):

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



PGP release keys (signed using 8B309F7251EE0BC8):

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



The vote will be open until the end of the week, 15nd June 2018.



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 
bcf602c7cd4ab662a7c4f208dee32fb8513e26c8 and published RC2 repository here:

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



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.1 systemvm templates are available from here:
http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/




Kind regards,

Paul Angus


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

Re: [VOTE] Apache CloudStack 4.11.1.0 LTS [RC1]

[Tutkowski, Mike]

+1 (binding)

I created a new cloud using commit 5f48487dc62fd1decaabc4ab2a10f549d6c82400 
(RC1). I ran the automated regression tests for managed storage. All tests 
passed.

On 5/24/18, 9:56 AM, "Paul Angus"  wrote:

Hi All,



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

[NB we know there are issues for Nuage to sort in this RC, but they will be 
well contained, so let’s test everything else  ]



Git Branch and Commit SH:


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

Commit: 5f48487dc62fd1decaabc4ab2a10f549d6c82400



Source release (checksums and signatures are available at the same

location):

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



PGP release keys (signed using 8B309F7251EE0BC8):

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



The vote will be open till end of next week, 1st June 2018.



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 
5f48487dc62fd1decaabc4ab2a10f549d6c82400 and published RC1 repository here:

http://packages.shapeblue.com/testing/4111rc1/



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.1 systemvm templates are available from here:
http://packages.shapeblue.com/systemvmtemplate/4.11.1-rc1/


Kind regards,

Paul Angus


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

Re: PR 2670: Removing an old, unused NetApp plug-in

[Tutkowski, Mike]

Including users@ on this (below).

On May 23, 2018, at 12:53 PM, Tutkowski, Mike 
<mike.tutkow...@netapp.com<mailto:mike.tutkow...@netapp.com>> wrote:

Hi everyone,

I opened the following PR today:

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

There is an old, what we believe to be unused, NetApp plug-in in the CloudStack 
codebase that I’d like to remove.

I’m sending this e-mail out for the following reasons:


1)   To see if, by chance, anyone is actually using this plug-in.

2)   To direct any potential code reviewers to this PR, where I have placed 
a couple questions about my commit.

To be absolutely clear here, this has nothing to do with any of the SolidFire 
plug-ins (only an old NetApp plug-in that hasn’t been updated in years and is 
probably not being used by anyone).

Thanks,
Mike

Re: PR 2670: Removing an old, unused NetApp plug-in

[Tutkowski, Mike]

Yeah, Paul, that JAR would no longer be needed.

> On May 23, 2018, at 1:01 PM, Paul Angus <paul.an...@shapeblue.com> wrote:
> 
> +1
> 
> There's a NetApp Jar in the nodist which is related I think - be nice to get 
> rid of that too.
> 
> paul.an...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
> 
> 
> 
> 
> -Original Message-
> From: Tutkowski, Mike <mike.tutkow...@netapp.com> 
> Sent: 23 May 2018 19:53
> To: dev@cloudstack.apache.org
> Subject: PR 2670: Removing an old, unused NetApp plug-in
> 
> Hi everyone,
> 
> I opened the following PR today:
> 
> https://github.com/apache/cloudstack/pull/2670
> 
> There is an old, what we believe to be unused, NetApp plug-in in the 
> CloudStack codebase that I’d like to remove.
> 
> I’m sending this e-mail out for the following reasons:
> 
> 
> 1)   To see if, by chance, anyone is actually using this plug-in.
> 
> 2)   To direct any potential code reviewers to this PR, where I have 
> placed a couple questions about my commit.
> 
> To be absolutely clear here, this has nothing to do with any of the SolidFire 
> plug-ins (only an old NetApp plug-in that hasn’t been updated in years and is 
> probably not being used by anyone).
> 
> Thanks,
> Mike

Re: PR 2670: Removing an old, unused NetApp plug-in

[Tutkowski, Mike]

I actually have no idea, Rafael. Nor does there seem to be anyone remaining at 
NetApp who knows about that plug-in.

> On May 23, 2018, at 1:22 PM, Rafael Weingärtner <rafaelweingart...@gmail.com> 
> wrote:
> 
> Those APi methods that you are removing as well (AssociateLunCmd.java,
> CreateLunCmd.java, CreateVolumeOnFilerCmd.java,  CreateVolumePoolCmd.java,
> DeleteVolumePoolCmd.java, DestroyLunCmd.java, DestroyVolumeOnFilerCmd.java,
> DissociateLunCmd.java, ListLunsCmd.java, ListVolumePoolsCmd.java, and so
> on), are they ony used for this NetApp plugin? It seems a considerable
> number of external API methods being removed.
> 
> I also have another question. Are all of these methods broken? I mean, do
> they work?
> 
>> On Wed, May 23, 2018 at 4:13 PM, Will Stevens <wstev...@cloudops.com> wrote:
>> 
>> +1
>> 
>> On Wed, May 23, 2018, 3:03 PM Gabriel Beims Bräscher, <
>> gabr...@pcextreme.nl>
>> wrote:
>> 
>>> I am +1 on removing it.
>>> 
>>>> On May 23, 2018 at 8:59 PM Paul Angus <paul.an...@shapeblue.com>
>> wrote:
>>>> 
>>>> 
>>>> +1
>>>> 
>>>> There's a NetApp Jar in the nodist which is related I think - be nice
>> to
>>> get rid of that too.
>>>> 
>>>> paul.an...@shapeblue.com
>>>> www.shapeblue.com
>>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>>> @shapeblue
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -Original Message-
>>>> From: Tutkowski, Mike <mike.tutkow...@netapp.com>
>>>> Sent: 23 May 2018 19:53
>>>> To: dev@cloudstack.apache.org
>>>> Subject: PR 2670: Removing an old, unused NetApp plug-in
>>>> 
>>>> Hi everyone,
>>>> 
>>>> I opened the following PR today:
>>>> 
>>>> https://github.com/apache/cloudstack/pull/2670
>>>> 
>>>> There is an old, what we believe to be unused, NetApp plug-in in the
>>> CloudStack codebase that I’d like to remove.
>>>> 
>>>> I’m sending this e-mail out for the following reasons:
>>>> 
>>>> 
>>>> 1) To see if, by chance, anyone is actually using this plug-in.
>>>> 
>>>> 2) To direct any potential code reviewers to this PR, where I have
>>> placed a couple questions about my commit.
>>>> 
>>>> To be absolutely clear here, this has nothing to do with any of the
>>> SolidFire plug-ins (only an old NetApp plug-in that hasn’t been updated
>> in
>>> years and is probably not being used by anyone).
>>>> 
>>>> Thanks,
>>>> Mike
>>> 
>> 
> 
> 
> 
> -- 
> Rafael Weingärtner