AW: CloudStack and Ansible

[peter.muryshkin]

Hi Rafael,

as a follow-up to your great talk at the CSEUG session: in your email you wrote,

"The Ansible implementation for ACS is very complete and robust. It made it 
possible for us to fully automate from metal to the service."

Which Ansible implementation do you mean? The one I can find addresses rather 
API usage [1]; for full automation there is probably more scripting required to 
setup the actual
cluster, possibly with some variations depending on the architecture.

[1] 
https://docs.ansible.com/ansible/latest/collections/ngine_io/cloudstack/index.html#plugins-in-ngine-io-cloudstack

kind regards
Peter

Von: Rafael del Valle 
Gesendet: Montag, 10. Mai 2021 21:14:12
An: users@cloudstack.apache.org
Cc: ivet.petr...@shapeblue.com
Betreff: Re: CloudStack and Ansible

Hi ,



The Ansible implementation for ACS is very complete and robust. It made it 
possible for us to fully automate from metal to the service.

I will be presenting this the 27th, and I am happy to participate on the post.

Regards,
Rafael




On Mon, 2021-05-10 05:22 PM, Rene Moser  wrote:
>
Hi Ivet
>
> On 10.05.21 16:52, Ivet Petrova wrote:
> > Hy everyone,
> >
> > I would like to prepare a blog post on CloudStack and Ansible use case. Are 
> > there any users here of this combination, who are willing to share insights 
> > (how you use it, why you selected it, etc.) and help me for the post?
>
> Yes, there are ;)
>
> Actually I am one of the authors and started the cloudstack ansible
> integration.
>
> When I started the project end of 2014, my vision was to not only
> install/update cloudstack (the application) and mysql with ansible, but
> a fully automated cloudstack setup including networking, storage, pod,
> host, cluster, configuration, etc.
>
> Even though I worked hard to cover all related APIs, I've never had the
> chance to actually deploy a cloudstack on the ground up and my daily
> work has shifted away from cloudstack admininistration [shapeblue didn't
> hire my ;)]
>
> Currently "only" using it in combination of exoscale to deploy and
> provision VMs, networks, autoscaling groups, security groups, ssh keys
> etc. So only user facing APIs.
>
> However, Raphael (who is also on the list I guess and in cc) realized my
> vision and did it (what I have heard from him). AFIACS he applied as
> speaker for the CSEUG on May 27th to show it to the community.
>
> Yours
> René
>

AW: [DISCUSS] Terraform CloudStack provider

[peter.muryshkin]

Hi all,

are there any updates regarding this topic i.e. migration of HashiCorp 
Terraform provider to Apache CloudStack, either registering it in HashiCorp's 
registry?

kind regards
Peter

Von: Rohit Yadav 
Gesendet: Freitag, 29. Januar 2021 17:14:05
An: Will Stevens; d...@cloudstack.apache.org
Cc: users; Niclas Lindblom; Pierre-Luc Dion
Betreff: Re: [DISCUSS] Terraform CloudStack provider

Hi Wido, Will, PL, all,

I think I can setup a repository and request ASF infra (who prefers a JIRA 
ticket) to enable PR/issue on it, anybody has an objection to a new 
apache/cloudstack-terraform repo to maintain the provider plugin?


Regards.


From: Will Stevens 
Sent: Friday, January 29, 2021 19:49
To: d...@cloudstack.apache.org 
Cc: users ; Rohit Yadav 
; Niclas Lindblom ; 
Pierre-Luc Dion 
Subject: Re: [DISCUSS] Terraform CloudStack provider

Hey PLD,
You may want to tune into this. I think you may be maintaining a fork based on 
this code, but I am not positive.

On Fri., Jan. 29, 2021, 6:07 a.m. Wido den Hollander, 
mailto:w...@widodh.nl>> wrote:


On 28/01/2021 10:55, Rohit Yadav wrote:
> Agree we can ask that.
>

Is infra from ASF the place to ask this?

Wido

>
> Regards.
>
> 
> From: Wido den Hollander mailto:w...@widodh.nl>>
> Sent: Wednesday, January 27, 2021 15:35
> To: Niclas Lindblom 
> mailto:niclas_lindb...@icloud.com>>; 
> users@cloudstack.apache.org 
> mailto:users@cloudstack.apache.org>>
> Cc: d...@cloudstack.apache.org 
> mailto:d...@cloudstack.apache.org>>
> Subject: Re: [DISCUSS] Terraform CloudStack provider
>
>
>
> On 1/27/21 12:18 AM, Niclas Lindblom wrote:
>> I can confirm that the Terraform plugin is working if it is already 
>> installed, since it was archived it no longer automatically downloads when 
>> applying unless manually installed.
>>
>>  From the Hashicorp website, it appears it was archived when they moved all 
>> plugins to their registry and needs an owner and an email to Hashicorp to be 
>> moved into to the registry and supported again when running Terraform. I use 
>> it regularly but haven’t got the technical skills to maintain the code so 
>> been hoping this would be resolved.
>>
>
> I mailed Hashicorp to ask about this:
>
> "Thanks for reaching out. The provider was archived because we launched
> the Terraform Registry last year which allows vendors to host and
> publish their own providers. We'd be happy to work with you to transfer
> the repository over to a CloudStack Github organization where you can
> build and publish releases to the registry.
>
> We'd also like to have CloudStack join our Technology partnership
> program so I can mark your Terraform provider as verified."
>
> So I think we don't need to do much technology-wise.
>
> I don't use Terraform and don't have a major stake in it, but I would
> hate to see the Provider being removed from Terraform.
>
> Should we request https://github.com/apache/cloudstack-terraform at
> infra and then host the Provider there?
>
> Wido
>
>> Niclas
>>
>>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>
rohit.ya...@shapeblue.com
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue



> On 26 Jan 2021, at 18:33, 
> christian.nieph...@zv.fraunhofer.de
>  wrote:
>>>
>>>
>>>
 On 26. Jan 2021, at 10:45, Wido den Hollander 
 mailto:w...@widodh.nl>> wrote:



 On 1/26/21 10:40 AM, 
 christian.nieph...@zv.fraunhofer.de
  wrote:
> On 25. Jan 2021, at 12:40, Abhishek Kumar 
> mailto:abhishek.ku...@shapeblue.com>> wrote:
>>
>> Hi all,
>>
>> Terraform CoudStack provider by Hashicorp is archived here 
>> https://github.com/hashicorp/terraform-provider-cloudstack
>>
>> Is anyone using or maintaining it?
>
> We are also using it heavily and are somewhat worried about the module 
> being archived.

 Agreed. But do we know why this has been done? What needs to be done to
 un-archive it?

 If it's just a matter of some love and attention we can maybe arrange
 something.

 Is it technically broken or just abandoned?
>>>
>>> This is just an educated guess, but given that we're not experiencing any 
>>> technical issues, I believe it has just been abandoned.
>>>
>>> Christian
>>>
>>>

 Wido

>
>> We're aware of Ansible CloudStack module 
>> (https://docs.ansible.com/ansible/latest/scenario_guides/guide_cloudstack.html)
>>  but are there any other alternatives of Terraform that you may be using 
>> with CloudStack?
>
> The ansible module is 

AW: [DISCUSS] Terraform CloudStack provider

[peter.muryshkin]

Hi there Rohit & all,

maybe worth to know, one of major dependencies used by the provider is a 
CloudStack stub which can be found here:

Project URL:
https://github.com/xanzy/go-cloudstack

Dependency link:
https://github.com/hashicorp/terraform-provider-cloudstack/blob/9ca483a88d6ba5559b241db5b537ad7eaaa417a1/vendor/modules.txt#L218

kind regards
Peter Muryshkin

Fraunhofer Cloud Services

Von: Rohit Yadav 
Gesendet: Montag, 1. Februar 2021 11:17:28
An: priv...@cloudstack.apache.org; d...@cloudstack.apache.org
Cc: users; Niclas Lindblom; Pierre-Luc Dion; Will Stevens
Betreff: Re: [DISCUSS] Terraform CloudStack provider

All,

I checked the repository again (was going to start a vote thread on the same), 
I think the terraform license could be an issue which is MPL. Can PMC guide us 
and comment if MPL is compatible with APL, and should we ask Hashicorp to 
relicense the repository before the CloudStack community and project takes over 
that repository?

The rough steps and tasks are:

  *   Discuss and resolve the issue of license compatbility and re-licensing to 
Apache License v2.0
  *   Create a new repository apache/cloudstack-terraform-provider that will 
takeover code (a git mirror or github repo transfer) from 
https://github.com/hashicorp/terraform-provider-cloudstack
  *   CloudStack project will join Hashicorp Technology partnership program 
(see Wido's comment [1][2])
  *   The community will maintain and help with releases of the terraform 
provider

The alternative is interested parties just join the 
terraform-provider-cloudstack repo as maintainer/committers. Thoughts? Thanks.

[1] https://markmail.org/message/2r5azbfugovx7ypw

[2] https://www.hashicorp.com/partners/become-a-partner#technology


Regards.


From: Will Stevens 
Sent: Saturday, January 30, 2021 02:16
To: Rohit Yadav 
Cc: d...@cloudstack.apache.org ; users 
; Niclas Lindblom ; 
Pierre-Luc Dion 
Subject: Re: [DISCUSS] Terraform CloudStack provider

I have no objection to that.

On Fri., Jan. 29, 2021, 11:14 a.m. Rohit Yadav, 
mailto:rohit.ya...@shapeblue.com>> wrote:
Hi Wido, Will, PL, all,

I think I can setup a repository and request ASF infra (who prefers a JIRA 
ticket) to enable PR/issue on it, anybody has an objection to a new 
apache/cloudstack-terraform repo to maintain the provider plugin?


Regards.

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





From: Will Stevens mailto:wstev...@cloudops.com>>
Sent: Friday, January 29, 2021 19:49
To: d...@cloudstack.apache.org 
mailto:d...@cloudstack.apache.org>>
Cc: users mailto:users@cloudstack.apache.org>>; 
Rohit Yadav mailto:rohit.ya...@shapeblue.com>>; 
Niclas Lindblom 
mailto:niclas_lindb...@icloud.com>>; Pierre-Luc 
Dion mailto:pd...@cloud.ca>>
Subject: Re: [DISCUSS] Terraform CloudStack provider

Hey PLD,
You may want to tune into this. I think you may be maintaining a fork based on 
this code, but I am not positive.

On Fri., Jan. 29, 2021, 6:07 a.m. Wido den Hollander, 
mailto:w...@widodh.nl>> wrote:


On 28/01/2021 10:55, Rohit Yadav wrote:
> Agree we can ask that.
>

Is infra from ASF the place to ask this?

Wido

>
> Regards.
>
> 
> From: Wido den Hollander mailto:w...@widodh.nl>>
> Sent: Wednesday, January 27, 2021 15:35
> To: Niclas Lindblom 
> mailto:niclas_lindb...@icloud.com>>; 
> users@cloudstack.apache.org 
> mailto:users@cloudstack.apache.org>>
> Cc: d...@cloudstack.apache.org 
> mailto:d...@cloudstack.apache.org>>
> Subject: Re: [DISCUSS] Terraform CloudStack provider
>
>
>
> On 1/27/21 12:18 AM, Niclas Lindblom wrote:
>> I can confirm that the Terraform plugin is working if it is already 
>> installed, since it was archived it no longer automatically downloads when 
>> applying unless manually installed.
>>
>>  From the Hashicorp website, it appears it was archived when they moved all 
>> plugins to their registry and needs an owner and an email to Hashicorp to be 
>> moved into to the registry and supported again when running Terraform. I use 
>> it regularly but haven’t got the technical skills to maintain the code so 
>> been hoping this would be resolved.
>>
>
> I mailed Hashicorp to ask about this:
>
> "Thanks for reaching out. The provider was archived because we launched
> the Terraform Registry last year which allows vendors to host and
> publish their own providers. We'd be happy to work with you to transfer
> the repository over to a CloudStack Github organization where you can
> build and publish releases to the registry.
>
> We'd also like to have CloudStack join our Technology partnership
> program so I can mark your Terraform provider as verified."
>
> So I think we don't need to do much technology-wise.
>
> I don't use Terraform and 

Minimal and meaningful recommended configuration in multi-hypervisor context

[peter.muryshkin]

Hi, all,

previously we have used a set of custom bash scripts to configure cloud-init to 
serve template creation both for KVM and VMWare Hypervisors. Though it's a 
maintenance effort and also compatibility risks.

Is it possible to have a standard YAML configuration in this case? Also without 
the multi-hypervisor context, I have hard times to find a minimal template by 
operation system. 

Typical requirements:

- have a custom SSH user
- synchronize network configuration and hostname with CloudStack

Following the manual the YAMl configuration seems quite simple from the first 
glance but then for example with Ubuntu I run into issues with the network 
configuration, like the interface does not come up.

Please help me to understand what can I expect, whether the configuration with 
cloud-init needs to be elaborate and maintain custom scripting for above use 
cases for every operation system and hypervisor or it's possible to tune common 
use cases in a simple way via the standard YAML?

How's your experience there, and are there shareable examples (maybe include 
them in the sources/documentation)? 

--
Peter Muryshkin
Fraunhofer-Gesellschaft e.V. / Zentrale
Abteilung C7 Kommunikationsmanagement
Schloss Birlinghoven, D-53754 Sankt Augustin peter.murysh...@zv.fraunhofer.de
Phone: (+49 2241) 14-1598
Fax:   (+49 2241) 14-4-1598

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

[peter.muryshkin]

Hi, Rakesh,

thanks!

After further digging the logs so far I can find:

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

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

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

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

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

kind regards
Peter



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

Hello Peter

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

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

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

--
Thanks and regards
Rakesh venkatesh

Troubleshooting the Exception "Unable to start VM instance"

[peter.muryshkin]

Hi, all,

sometimes the system can't start a VM instance (a 530 error).
In the logs there is the following trace - how to troubleshoot it and 
understand which circumstances lead to it?


com.cloud.utils.exception.CloudRuntimeException: Unable to start VM instance
at 
com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4889)
at sun.reflect.GeneratedMethodAccessor433.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
at 
com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5047)
at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:615)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:563)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

kind regards
Peter

AW: Resource type for an ACL? (API)

[peter.muryshkin]

Hi, all,

here a follow-up on ACL tagging.

Following Andrea's suggestion:

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

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

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

I have tried the following as domain master user:

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

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

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

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

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

kind regards
Peter 





kind regards
Peter














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

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


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

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

Fast access to specific templates vs. secondary storage

[peter.muryshkin]

Hi all,

naturally the secondary storage is slower than the primary one.

Now what if you need some VMs to load very fast i.e. for CI/CD environment 
purposes (that is, a build/test iterations requires one or more one-way fresh 
VMs?)

Is there currently a way to have some VM templates in the primary storage?

kind regards
Peter

AW: committer with merge rights on cloudstack-www

[peter.muryshkin]

Hi, Andrija and Paul,

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

Here I read:

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

Well.. any ideas how to use Marvin then?

kind regards
Peter

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

Is the following (what I did actually) enough ?

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

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

Cheers

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




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

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

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

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



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




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

Hi, Paul,

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

Please help.

kind regards
Peter


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

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


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




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

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


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




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

Hi Paul,

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

cu Swen

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

Hi Swen,

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

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


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

Paul.


paul.an...@shapeblue.com
www.shapeblue.com
Amadeus House, 

AW: committer with merge rights on cloudstack-www

[peter.muryshkin]

Hi, Paul,

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

Please help.

kind regards
Peter


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

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


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




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

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


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




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

Hi Paul,

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

cu Swen

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

Hi Swen,

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

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


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

Paul.


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




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

Dear community,

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

cu Swen

Assess job queues and their load balancing on management servers

[peter.muryshkin]

Hi, all,

in our setup (CS 4.10) we have noticed that one of two CS management servers 
have very long prosecsing time (over 10 minutes, after that we consider it as 
timeout) but both servers are active.

While our working assumption is that the job queue of the problem server gets 
too long i.e. the load distribution does not work properly - how to assess and 
configure this job load balancing?

kind regards
Peter

AW: Resource type for an ACL? (API)

[peter.muryshkin]

Hi, Anurag,

I have tested so far only as domain admin.

kind regards
Peter

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

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


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

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

AW: Resource type for an ACL? (API)

[peter.muryshkin]

Hi, Anurag,

thank you for your quick response - as I've found out, I am actually NOT able 
to create a tag.

Error message:
"The user is not allowed to request the API command or the API command does not 
exist"

But, I tried it as a root user of an account - is tagging then allowed for the 
global root admin only?

Call:
result = self.cs.create_tags(resourceids=self.firewallruleid, 
resourcetype='FirewallRule', tags = {'foo':'bar'})

kind regards
Peter


Von: Anurag Awasthi [anurag.awas...@shapeblue.com]
Gesendet: Freitag, 5. April 2019 07:04
An: Muryshkin, Peter; users@cloudstack.apache.org
Betreff: Re: Resource type for an ACL? (API)

Hi Peter,

Welcome to the community!

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

Kind Regards,
Anurag

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





From: peter.murysh...@zv.fraunhofer.de 
Sent: Thursday, April 4, 2019 8:31 PM
To: users@cloudstack.apache.org
Subject: Resource type for an ACL? (API)

Hi, all,

while I can create a tag for a firewall rule, I can't find the resource name 
for network ACL item.

Is it anyhow possible to set a tag there?


P.S. This is my first time I post to this mailing list, so hello everybody - 
Apache CloudStack is really great and from the first impression the community 
seems to be very enjoyable!

kind regards
Peter

Resource type for an ACL? (API)

[peter.muryshkin]

Hi, all,

while I can create a tag for a firewall rule, I can't find the resource name 
for network ACL item.

Is it anyhow possible to set a tag there?


P.S. This is my first time I post to this mailing list, so hello everybody - 
Apache CloudStack is really great and from the first impression the community 
seems to be very enjoyable!

kind regards
Peter