[GitHub] cloudstack issue #872: Strongswan vpn feature

[jayapalu]

Github user jayapalu commented on the issue:

https://github.com/apache/cloudstack/pull/872
  
@swill 
If your connection is not coming up without IKE DH in customer gateway 
configuration then try configuring IKE DH in customer gateway value from  
UI/API.
In strongswan 5.2 ipsec, customer gateway configuration (at least in one 
customer gateway)need to configured IKE DH value (modp1024), without this the 
connection  is not coming up. 

Config file VR example:
 cat /etc/ipsec.d/ipsec.vpn-10.147.46.103.conf 
#conn for vpn-10.147.46.103
conn vpn-10.147.46.103
 left=10.147.46.104
 leftsubnet=10.2.0.0/16
 leftnexthop=10.147.46.1
 right=10.147.46.103
 rightsubnet=10.1.0.0/16
 type=tunnel
 authby=secret
 keyexchange=ike
 ike=3des-md5-modp1024
 ikelifetime=24h
 esp=3des-md5
 lifetime=1h
 pfs=no
 keyingtries=2
 auto=start
 forceencaps=no



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

[GitHub] cloudstack issue #1451: CLOUDSTACK-9319: Use timeout when applying config to...

[ozhanrk]

Github user ozhanrk commented on the issue:

https://github.com/apache/cloudstack/pull/1451
  
Hi, last week we experience some problems because of the timeouts which 
mentioned on this PR. Could we get this PR to upcoming versions asap please. 
Without this timeout configuration functionality working, its very hard to make 
upgrades on VR, timeout issue generates real headaches.


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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@jburwell yes we might have to further investigate this. I am waiting for 
info about the global params from @pdion891 to further this.
I think it will require a fix in upgrade scripts as the original 
authenticator should be preserved.


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

[GitHub] cloudstack issue #1678: CLOUDSTACK-9503: Increased the VR script timeout. Mo...

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1678
  
@jburwell  ticket filed to refactor Script and SshHelper to use Duration. 
https://issues.apache.org/jira/browse/CLOUDSTACK-9508


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

[GitHub] cloudstack pull request #1678: CLOUDSTACK-9503: Increased the VR script time...

[abhinandanprateek]

Github user abhinandanprateek commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1678#discussion_r80427974
  
--- Diff: 
core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java ---
@@ -374,9 +375,9 @@ private Answer execute(AggregationControlCommand cmd) {
 FileConfigItem fileConfigItem = new 
FileConfigItem(VRScripts.CONFIG_CACHE_LOCATION, cfgFileName, sb.toString());
 ScriptConfigItem scriptConfigItem = new 
ScriptConfigItem(VRScripts.VR_CFG, "-c " + VRScripts.CONFIG_CACHE_LOCATION + 
cfgFileName);
 // 120s is the minimal timeout
-int timeout = answerCounts * _eachTimeout;
-if (timeout < 120) {
-timeout = 120;
+Duration timeout = 
_eachTimeout.withDurationAdded(_eachTimeout.getStandardSeconds(), answerCounts);
--- End diff --

@jburwell the java Duration that has multipliedBy is available from Java 8. 
Right now we are using joda.time.


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

[GitHub] cloudstack issue #1659: CLOUDSTACK-9339 Virtual Routers don't handle Multipl...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1659
  
@jburwell i am investigating them. Just so you know, blueorangutan is 
running full smoke test suite. Similar failures are seen in other PR as well. 
So some of the tests may have been failing for some time and need to be fixed.

From the above list of failures test_router_dhcphosts are due to test 
errors that is being addressed by https://github.com/apache/cloudstack/pull/1683

I have addressed below two test failures. support for internal LB was not 
added in the logic creating ips.json databag, I made a fix for that as well.

test_02_internallb_roundrobin_1RVPC_3VM_HTTP_port80
test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80

rest of the failures i am investigating if they are regressions, and test 
failures.


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

RE: vmware macchinina template

[Paul Angus]

Hi Nux,

No, It doesn’t seem to be in there either. ☹


Kind regards,

Paul Angus

From: Nux! [mailto:n...@li.nux.ro]
Sent: 23 September 2016 21:16
To: Paul Angus ; dev@cloudstack.apache.org
Subject: Re: vmware macchinina template

Hi,

I am away for a few days, won't have a chance to look at this till next week. 
There should be an 'old' dir on the same location, can you give that a try, see 
if it has the driver?

--
Sent from my mobile device. Please excuse my brevity.
On 23 September 2016 13:05:26 CEST, Paul Angus 
mailto:paul.an...@shapeblue.com>> wrote:
Hi Nux,


How are you doing?


I’m fixing the marvin tests to point to 
http://dl.openvm.eu/cloudstack/macchinina/x86_64/macchinina-vmware.ova


But Serg points out that the vmware template doesn’t have an E1000 (intel 
pro/1000) driver in it so can’t enable interfaces.
Could you fix or let me know how I can build a template to pass back to you pls.






Kind regards,


Paul Angus



paul.an...@shapeblue.com
www.shapeblue.com
@shapeblue




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

[GitHub] cloudstack issue #1688: Marvin Tests: Fix VPC network offering selection

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1688
  
@PaulAngus can you please investigate/address the Jenkins build failure?


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

[GitHub] cloudstack issue #1652: Marvin Tests: Fix VPC network offering selection .

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1652
  
@PaulAngus is their PR superceded by #1688?


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

[GitHub] cloudstack pull request #1691: fix ping tests to properly recognise successf...

[PaulAngus]

GitHub user PaulAngus opened a pull request:

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

fix ping tests to properly recognise successful ping test

fix ping tests to properly recognise successful ping test (on 4.8 branch)

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

$ git pull https://github.com/shapeblue/cloudstack 4.8-fixpingtests

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

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

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

This closes #1691


commit 95abb6efc350189cb2be0cfd655c1205ced42155
Author: Rohit Yadav 
Date:   2016-04-21T10:13:04Z

CLOUDSTACK-9361: Centrally handle API validations

Validate API arguments based on annotations. Introduces:
- NotNullOrEmpty: for doing null and empty string checks
- PositiveNumber: number > 0 (natural number)

Signed-off-by: Rohit Yadav 

commit 4347776ac6ef9ae86fb016862f4a6b2376f8319a
Author: Rohit Yadav 
Date:   2016-03-15T08:16:06Z

CLOUDSTACK-8562: DB-Backed Dynamic Role Based API Access Checker

This feature allows root administrators to define new roles and associate 
API
permissions to them.

A limited form of role-based access control for the CloudStack management 
server
API is provided through a properties file, commands.properties, embedded in 
the
WAR distribution. Therefore, customizing API permissions requires unpacking 
the
distribution and modifying this file consistently on all servers. The old 
system
also does not permit the specification of additional roles.

FS:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Dynamic+Role+Based+API+Access+Checker+for+CloudStack

DB-Backed Dynamic Role Based API Access Checker for CloudStack brings 
following
changes, features and use-cases:
- Moves the API access definitions from commands.properties to the mgmt 
server DB
- Allows defining custom roles (such as a read-only ROOT admin) beyond the
  current set of four (4) roles
- All roles will resolve to one of the four known roles types (Admin, 
Resource
  Admin, Domain Admin and User) which maintains this association by 
requiring
  all new defined roles to specify a role type.
- Allows changes to roles and API permissions per role at runtime including 
additions or
  removal of roles and/or modifications of permissions, without the need
  of restarting management server(s)

Upgrade/installation notes:
- The feature will be enabled by default for new installations, existing
  deployments will continue to use the older static role based api access 
checker
  with an option to enable this feature
- During fresh installation or upgrade, the upgrade paths will add four 
default
  roles based on the four default role types
- For ease of migration, at the time of upgrade commands.properties will be 
used
  to add existing set of permissions to the default roles. cloud.account
  will have a new role_id column which will be populated based on default 
roles
  as well

Dynamic-roles migration tool: scripts/util/migrate-dynamicroles.py
- Allows admins to migrate to the dynamic role based checker at a future 
date
- Performs a harder one-way migrate and update
- Migrates rules from existing commands.properties file into db and 
deprecates it
- Enables an internal hidden switch to enable dynamic role based checker 
feature

Signed-off-by: Rohit Yadav 

commit afcbd270b2eb9086a76dda83c0f9ba2e034b0afd
Author: Rohit Yadav 
Date:   2016-04-29T19:10:47Z

CLOUDSTACK-8562: Deprecate commands.properties

- Removes commands.properties file
- Fixes apidocs and marvin to be independent of commands.properties usage
- Removes bundling of commands.properties in deb/rpm packaging
- Removes file references across codebase

Signed-off-by: Rohit Yadav 

commit 003b97bcffe640e38d089c98e8215de4c8a805e6
Author: Rohit Yadav 
Date:   2016-05-04T09:58:12Z

maven: Fix jstl version usage

This would fix regression from recent mvn version changes. Without this
patch users get redirected to error.jsp as jstl-1.2 jar is not installed

Signed-off-by: Rohit Yadav 

commit dc5b52937bf9c14634452ed47a851a689a3015c4
Author: Will Stevens 
Date:   2016-05-11T05:32:02Z

Merge release branch 4.8 to master

* 4.8:
  When no zone name is available display a default

commit 71c9c90e0c81ea9e0f90ab71d3430d62cd8fa02e
Author: Nick Livens 
Date:   2016-05-02T11:16:14Z

CLOUDSTACK-9365 : updateVirtualMachine with userdata should not error when 
a VM is attached to multiple networks from which one or more doesn't support 
userdata

commit 9df51faa8a2f0678e7927ac6ef23752b1eae8f71
Author: rahul singal 
Date:   2016-05-09T11:24:5

[GitHub] cloudstack pull request #1691: fix ping tests to properly recognise successf...

[PaulAngus]

Github user PaulAngus closed the pull request at:

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


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

[GitHub] cloudstack pull request #1692: fix ping tests to properly recognise successf...

[PaulAngus]

GitHub user PaulAngus opened a pull request:

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

fix ping tests to properly recognise successful ping test

fix ping tests to properly recognise successful ping test (on 4.8 branch)

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

$ git pull https://github.com/shapeblue/cloudstack 4.8-marvinpingtests

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

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

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

This closes #1692


commit 3cc59c1165e411610c014b162fc0d1583d6a70d8
Author: Paul Angus 
Date:   2016-09-26T11:08:41Z

fix ping tests to properly recognise successful ping test




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

ACS 4.9 + VMware: Failed to deploy VPC VR due to IPAssoc failure

[Prashanth Manthena]

Hi All,

We are hitting an issue where VPC VR is failing to come up due to IpAssoc
failure in ACS+VMware setup.

We have tried with the following system VM templates:

http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-vmware.ova

http://cloudstack.apt-get.eu/templates/4.7/systemvm64template-2016-05-18-4.7.0-vmware.ova


Is there a more latest system VM template that fixes this issue ?


Here is the error log:

[1:00]
IpAssocVpcCommand) (logid:f727c105) Prepare Ip Assoc failure on applying
one ip due to exception:
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with.
   at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkElementCommand(VmwareResource.java:917)
   at
com.cloud.hypervisor.vmware.resource.VmwareResource.prepareCommand(VmwareResource.java:803)
   at
com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.executeRequest(VirtualRoutingResource.java:97)
   at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:387)
   at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
   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:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
   at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
   at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)
2016-09-26 02:30:22,053 ERROR [c.c.a.r.v.VirtualRoutingResource]
(DirectAgent-80:ctx-d0fb047f 10.31.56.182, job-65/job-66, cmd:
IpAssocVpcCommand) (logid:f727c105) Failed to prepare VR command due to
com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
associate/disassociate IP with.

With regards,
Prashanth

Re: ACS 4.9 + VMware: Failed to deploy VPC VR due to IPAssoc failure

[Murali Reddy]

findRouterEthDeviceIndex() in VmwareResource returned -1.


Looks like CLOUDSTACK-9491: incorrect parsing of device list to find ethernet 
index of plugged NIC

There is a PR https://github.com/apache/cloudstack/pull/1681



On 26/09/16, 5:13 PM, "Prashanth Manthena" 
 wrote:

>Hi All,
>
>We are hitting an issue where VPC VR is failing to come up due to IpAssoc
>failure in ACS+VMware setup.
>
>We have tried with the following system VM templates:
>
>http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-vmware.ova
>
>http://cloudstack.apt-get.eu/templates/4.7/systemvm64template-2016-05-18-4.7.0-vmware.ova
>
>
>Is there a more latest system VM template that fixes this issue ?
>
>
>Here is the error log:
>
>[1:00]
>IpAssocVpcCommand) (logid:f727c105) Prepare Ip Assoc failure on applying
>one ip due to exception:
>com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
>associate/disassociate IP with.
>   at
>com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkElementCommand(VmwareResource.java:917)
>   at
>com.cloud.hypervisor.vmware.resource.VmwareResource.prepareCommand(VmwareResource.java:803)
>   at
>com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.executeRequest(VirtualRoutingResource.java:97)
>   at
>com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:387)
>   at
>com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
>   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:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at
>java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
>   at
>java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
>   at
>java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at
>java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
>2016-09-26 02:30:22,053 ERROR [c.c.a.r.v.VirtualRoutingResource]
>(DirectAgent-80:ctx-d0fb047f 10.31.56.182, job-65/job-66, cmd:
>IpAssocVpcCommand) (logid:f727c105) Failed to prepare VR command due to
>com.cloud.exception.InternalErrorException: Failed to find DomR VIF to
>associate/disassociate IP with.
>
>With regards,
>Prashanth

Zephyr: Test Management plugin for JIRA

[Boris Stoyanov]

Hi there,

I’d like to purpose a plugin for JIRA that would make our live easier during 
release testing phase. It’s called Zephyr and it has been part of the Atlassian 
eco-system for quite a while. Most of us have already worked with it or at 
least got in touch with it already.
What offers is easy planning of test cycles, test case management and 
integration of automated tests.

I was curious, being part of the ASF and having a massive public JIRA, would 
Cloudstack be able to get free license for it’s users in JIRA?

There are a few features of the product, which we could start using almost 
immediately like:

  *   Marvin test execution integration - Zephyr has an integration API (called 
ZAPI) which we could use to store results from the marvin tests we execute.
 *   ToDo: Need to create ZAPI integration call at the end of each tests to 
store results and test attributes
  *   Keep track of manual testing activities
  *   Release Testing Management and Organization - It creates items in JIRA 
such as test plans and results that could be scheduled/executed and offers 
transparent way to manage them
  *   Log PR testing results in JIRA and optionally link them to the JIRA 
ID(same way we do with BlueOrangutan, but instead loggin results in message in 
the PR, we create a test plan for the PR and add results there)


Checkout it’s official page in the Atlassian Marketplace
https://marketplace.atlassian.com/plugins/com.thed.zephyr.je/server/overview

Please share thoughts/concerns.

Thanks,
Boris Stoyanov

boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@abhinandanprateek  I did replace the following 4 settings by the original 
values. But after restarting jetty I'm unable to login, but this time the 
behavior is a bit different, it look like it doesn't try to login, no log or 
message in the UI.

```
update configuration set value=null where 
name='user.password.encoders.exclude';
update configuration set value='SHA256SALT,MD5,LDAP,PLAINTEXT' where 
name='user.authenticators.order';
update configuration set value=null where 
name='user.authenticators.exclude';
update configuration set value='SHA256SALT,MD5,LDAP,PLAINTEXT' where 
name='user.password.encoders.order';
```

Could it be possible the  authentication order is not followed at the 
login? if the password does not meet ``PBKDF2`` requirement, which is the first 
in the order list of 4.9.0, shouldn't try with the next encoder in the list and 
so on?




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

Re: 4.8, 4.9, and master Branches Frozen for Testing

[Will Stevens]

Yes, I think it is important that you or Rajani sign off on anything that
gets in while branches are frozen so you guys can stay on top of what goes
in.

Thanks for all the hard work team.  :)

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Mon, Sep 26, 2016 at 2:10 AM, John Burwell 
wrote:

> All,
>
> Per our release schedule [1], the 4.8, 4.9, and master branches are frozen
> for testing.  There are some straggling PRs that Rajani and I are working
> to merge.  Is it acceptable to everyone that for the next two (2) weeks,
> all PRs require not only 2 LGTMs, but approval by Rajani or I to be merged
> to these branches?  To be clear, we don’t have to perform the merges,
> simply give a thumbs up.
>
> Thanks,
> -John
> john.burw...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London VA WC2N 4HSUK
> @shapeblue
>
>
>
>

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
LGTM for code -- kicking tests


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

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[jburwell]

Github user jburwell commented on the issue:

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


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

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[blueorangutan]

Github user blueorangutan commented on the issue:

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


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

[GitHub] cloudstack issue #1689: Switched to the official SolidFire SDK for Python

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1689
  
@mike-tutkowski could you please amend the test result details to this PR?


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

[GitHub] cloudstack issue #1677: CLOUDSTACK-8830 - [Vmware] VM snapshot fails for 12 ...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1677
  
@jburwell This issue doesn't manifest on ESX 5.5. We already confirmed it 
resolves the issue to up to 4.5 branch. test_vm_snapshot which fails on ESX 6 
now works fine. I can post test suite results shortly


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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[dagsonstebo]

Github user dagsonstebo commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@abhinandanprateek @jburwell @pdion891 - my twopence worth - I've come 
across issues with this on two uprade projects in the last 8-10 months. Both 
cases were CCP to ACS upgrades:

1) In the first case we hit an issue where the admin account could log in - 
but no users. We carried out a preliminary check of this, and the suspicion was 
on changes in the MD5 authenticator - but the client eventually chose to just 
reset all users passwords, hence no accurate RCA carried out.

2) In the second, more recent case the client wanted to use either 
PLAINTEXT or MD5 authenticators, hence we updated the authenticators order 
similar to @pdion891 did above. During troubleshooting of this trace level 
logging showed the authenticator order in ACS4.9 was respected, no issues 
found. RCA of the underlying issue concluded with it being a user configuration 
and usage issue rather than a bug.


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

[GitHub] cloudstack issue #1677: CLOUDSTACK-8830 - [Vmware] VM snapshot fails for 12 ...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1677
  
@serg38 I understand it is not an issue on ESXi 5.5.  From a regression 
test perspective, we need to run to regression tests to ensure this change does 
not introduce an issue with ESXi 5.5.  Which tests are you running to verify 
the change on ESXi 6?  I will run those on 5.5 to verify that no regressions 
have been introduced.


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

[GitHub] cloudstack issue #1659: CLOUDSTACK-9339 Virtual Routers don't handle Multipl...

[ustcweizhou]

Github user ustcweizhou commented on the issue:

https://github.com/apache/cloudstack/pull/1659
  
@murali-reddy FYI
```
diff --git a/systemvm/patches/debian/config/opt/cloud/bin/merge.py 
b/systemvm/patches/debian/config/opt/cloud/bin/merge.py
index c6ed190..7f3dbbc 100755
--- a/systemvm/patches/debian/config/opt/cloud/bin/merge.py
+++ b/systemvm/patches/debian/config/opt/cloud/bin/merge.py
@@ -217,6 +217,9 @@ class updateDataBag:
 elif (self.qFile.data['cmd_line']['type'] == "dhcpsrvr"):
 self.processCLItem('0', "guest")
 self.processCLItem('1', "control")
+elif (self.qFile.data['cmd_line']['type'] == "ilbvm"):
+self.processCLItem('0', "guest")
+self.processCLItem('1', "control")
 return cs_cmdline.merge(dbag, self.qFile.data)

 def processCLItem(self, num, nw_type):
```


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

[GitHub] cloudstack issue #1659: CLOUDSTACK-9339 Virtual Routers don't handle Multipl...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1659
  
@ustcweizhou thanks, i have fixed it earlier today and tested, am trying to 
fix other test failures and re-run the CI


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

[GitHub] cloudstack issue #1659: CLOUDSTACK-9339 Virtual Routers don't handle Multipl...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1659
  
#1692 has been opened that replaces #1683 to address the ping test issue on 
the 4.8, 4.9, and master branches rather just master for the original PR.  
Testing the PR now.


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

[GitHub] cloudstack issue #1683: fix ping tests to properly recognise successful ping...

[jburwell]

Github user jburwell commented on the issue:

https://github.com/apache/cloudstack/pull/1683
  
Since this PR is superseded by #1693, @PaulAngus can you close this one?


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

[GitHub] cloudstack issue #1677: CLOUDSTACK-8830 - [Vmware] VM snapshot fails for 12 ...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1677
  
@jburwell  test_vm_snaphot only. Originally all 4 tests inside it would 
fail. With the fix one test still fails but it is unrelated to this issue and a 
conversation started in PR871. We would need either revert PR871 or open a new 
PR to resolve 4th test failure.

Test to create VM snapshots ... === TestName: test_01_create_vm_snapshots | 
Status : SUCCESS ===
Test to revert VM snapshots ... === TestName: test_02_revert_vm_snapshots | 
Status : SUCCESS ===
Test to delete vm snapshots ... === TestName: test_03_delete_vm_snapshots | 
Status : SUCCESS ===
=== TestName: test_01_test_vm_volume_snapshot | Status : EXCEPTION ===




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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@dagsonstebo, did you upgrade to 4.9 ?  So far, I had no authentication 
issue upgrading to 4.7.


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

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[blueorangutan]

Github user blueorangutan commented on the issue:

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


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

[GitHub] cloudstack issue #1681: CLOUDSTACK-9491: incorrect parsing of device list to...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1681
  
@sateesh-chodapuneedi  added optimization for now, but its better we 
eliminate the whole logic of finding device index from the VR.


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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[dagsonstebo]

Github user dagsonstebo commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@pdion891 in my list above:

1) Was an upgrade CCP4.5.1 to ACS4.5.2 - and this was where we potentially 
saw a bug, but never proven.
2) Was an upgrade CCP3.0.7 to ACS4.9.0 - no issues found.


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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@dagsonstebo for your scenario 2 can you get the count of global settings ? 

via cloudmonkey as admin:
```
list configurations
```
You should have a count of about 468.

Also this current PR did apply some changes from the Config.java that were 
not applied in your upgrades. I have test upgrade path without this fix and I 
had no issues, but we end up with missing configurations entrees.


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

[GitHub] cloudstack issue #1684: CLOUDSTACK-9489: the new config vars that are added ...

[dagsonstebo]

Github user dagsonstebo commented on the issue:

https://github.com/apache/cloudstack/pull/1684
  
@pdion891 - client system so limited access, not got cloudmonkey access but 
here's what's in the DB:

mysql> select name from configuration;
| name|
| account.cleanup.interval|
| affinity.processors.exclude |
| affinity.processors.order   |
| agent.lb.enabled|
| agent.load.threshold|
| alert.email.addresses   |
| alert.email.sender  |
| alert.purge.delay   |
| alert.purge.interval|
| alert.smtp.connectiontimeout|
| alert.smtp.host |
| alert.smtp.password |
| alert.smtp.port |
| alert.smtp.timeout  |
| alert.smtp.useAuth  |
| alert.smtp.username |
| alert.wait  |
| allow.public.user.templates |
| allow.subdomain.network.access  |
| allow.user.create.projects  |
| allow.user.expunge.recover.vm   |
| allow.user.view.destroyed.vm|
| api.checkers.exclude|
| api.throttling.cachesize|
| api.throttling.enabled  |
| api.throttling.interval |
| api.throttling.max  |
| apply.allocation.algorithm.to.pods  |
| backup.snapshot.wait|
| baremetal.ipmi.fail.retry   |
| baremetal.ipmi.lan.interface|
| blacklisted.routes  |
| capacity.check.period   |
| capacity.skipcounting.hours |
| check.pod.cidrs |
| check.txn.before.sending.agent.commands |
| cloud.dns.name  |
| cloud.identifier|
| cloudbyte.management.apikey |
| cloudbyte.management.ip |
| cluster.cpu.allocated.capacity.disablethreshold |
| cluster.cpu.allocated.capacity.notificationthreshold|
| cluster.heartbeat.interval  |
| cluster.heartbeat.threshold |
| cluster.localStorage.capacity.notificationthreshold |
| cluster.memory.allocated.capacity.disablethreshold  |
| cluster.memory.allocated.capacity.notificationthreshold |
| cluster.message.timeout.seconds |
| cluster.storage.allocated.capacity.notificationthreshold|
| cluster.storage.capacity.notificationthreshold  |
| cluster.storage.operations.exclude  |
| concurrent.snapshots.threshold.perhost  |
| console.proxy.allocator.exclude |
| consoleproxy.capacity.standby   |
| consoleproxy.capacityscan.interval  |
| consoleproxy.cmd.port   |
| consoleproxy.disable.rpfilter   |
| consoleproxy.launch.max |
| consoleproxy.loadscan.interval  |
| consoleproxy.management.state   |
| consoleproxy.management.state.last  |
| consoleproxy.restart|
| consoleproxy.service.offering   |
| consoleproxy.session.max|
| consoleproxy.session.timeout|
| consoleproxy.url.domain |
| control.cidr|
| control.gateway |
| copy.volume.wait

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[jburwell]

Github user jburwell commented on the issue:

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


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

[GitHub] cloudstack issue #1692: fix ping tests to properly recognise successful ping...

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1692
  
@jburwell a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been 
kicked to run smoke tests


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

[GitHub] cloudstack pull request #1693: CLOUDSTACK-9505: Fix test_deploy_vgpu_enabled...

[nvazquez]

GitHub user nvazquez opened a pull request:

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

CLOUDSTACK-9505: Fix test_deploy_vgpu_enabled tests cleanup

JIRA TICKET: https://issues.apache.org/jira/browse/CLOUDSTACK-9505

## Description
Cleanup resources after running `test_deploy_vgpu_enabled.py`. Although 
test passes, resources are left and need to be cleaned up

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

$ git pull https://github.com/nvazquez/cloudstack fix3dputest

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

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

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

This closes #1693


commit 8f35e8d4125ab1968dd258c40674c0709c06
Author: nvazquez 
Date:   2016-09-26T16:08:31Z

CLOUDSTACK-9505: Fix test_deploy_vgpu_enabled tests cleanup




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

[GitHub] cloudstack issue #1689: Switched to the official SolidFire SDK for Python

[mike-tutkowski]

Github user mike-tutkowski commented on the issue:

https://github.com/apache/cloudstack/pull/1689
  
TestAddRemoveHosts.py:

test_add_remove_host_with_solidfire_plugin_1 
(TestAddRemoveHosts.TestAddRemoveHosts) ... === TestName: 
test_add_remove_host_with_solidfire_plugin_1 | Status : SUCCESS ===
ok
test_add_remove_host_with_solidfire_plugin_2 
(TestAddRemoveHosts.TestAddRemoveHosts) ... === TestName: 
test_add_remove_host_with_solidfire_plugin_2 | Status : SUCCESS ===
ok
test_add_remove_host_with_solidfire_plugin_3 
(TestAddRemoveHosts.TestAddRemoveHosts) ... === TestName: 
test_add_remove_host_with_solidfire_plugin_3 | Status : SUCCESS ===
ok
test_add_remove_host_with_solidfire_plugin_4 
(TestAddRemoveHosts.TestAddRemoveHosts) ... === TestName: 
test_add_remove_host_with_solidfire_plugin_4 | Status : SUCCESS ===
ok

--
Ran 4 tests in 3621.836s

OK

TestManagedSystemVMs.py:

test_01_create_system_vms_on_managed_storage 
(TestManagedSystemVMs.TestManagedSystemVMs) ... === TestName: 
test_01_create_system_vms_on_managed_storage | Status : SUCCESS ===
ok
test_02_failure_to_create_service_offering_with_customized_iops 
(TestManagedSystemVMs.TestManagedSystemVMs) ... === TestName: 
test_02_failure_to_create_service_offering_with_customized_iops | Status : 
SUCCESS ===
ok

--
Ran 2 tests in 2637.630s

OK

TestSnapshots.py:

test_01_create_volume_snapshot_using_sf_snapshot 
(TestSnapshots.TestSnapshots) ... === TestName: 
test_01_create_volume_snapshot_using_sf_snapshot | Status : SUCCESS ===
ok
test_02_create_volume_snapshot_using_sf_volume 
(TestSnapshots.TestSnapshots) ... === TestName: 
test_02_create_volume_snapshot_using_sf_volume | Status : SUCCESS ===
ok
test_03_create_volume_snapshot_using_sf_volume_and_sf_snapshot 
(TestSnapshots.TestSnapshots) ... === TestName: 
test_03_create_volume_snapshot_using_sf_volume_and_sf_snapshot | Status : 
SUCCESS ===
ok

--
Ran 3 tests in 7510.549s

OK

TestVMMigrationWithStorage.py:

test_01_storage_migrate_root_and_data_disks 
(TestVMMigrationWithStorage.TestVMMigrationWithStorage) ... === TestName: 
test_01_storage_migrate_root_and_data_disks | Status : SUCCESS ===
ok
test_02_storage_migrate_root_and_data_disks 
(TestVMMigrationWithStorage.TestVMMigrationWithStorage) ... === TestName: 
test_02_storage_migrate_root_and_data_disks | Status : SUCCESS ===
ok
test_03_storage_migrate_root_and_data_disks_fail 
(TestVMMigrationWithStorage.TestVMMigrationWithStorage) ... === TestName: 
test_03_storage_migrate_root_and_data_disks_fail | Status : SUCCESS ===
ok
test_04_storage_migrate_root_disk_fails 
(TestVMMigrationWithStorage.TestVMMigrationWithStorage) ... === TestName: 
test_04_storage_migrate_root_disk_fails | Status : SUCCESS ===
ok
test_05_storage_migrate_data_disk_fails 
(TestVMMigrationWithStorage.TestVMMigrationWithStorage) ... === TestName: 
test_05_storage_migrate_data_disk_fails | Status : SUCCESS ===
ok

--
Ran 5 tests in 3688.422s

OK

TestVMSnapshots.py:

test_01_take_VM_snapshot (TestVMSnapshots.TestVMSnapshots) ... === 
TestName: test_01_take_VM_snapshot | Status : SUCCESS ===
ok
test_02_take_VM_snapshot_with_data_disk (TestVMSnapshots.TestVMSnapshots) 
... === TestName: test_02_take_VM_snapshot_with_data_disk | Status : SUCCESS ===
ok

--
Ran 2 tests in 777.188s

OK

TestVolumes.py (with resigning):

test_00_check_template_cache (TestVolumes.TestVolumes) ... === TestName: 
test_00_check_template_cache | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === 
TestName: test_01_attach_new_volume_to_stopped_VM | Status : SUCCESS ===
ok
Attach, detach, and attach volume to a running VM ... === TestName: 
test_02_attach_detach_attach_volume | Status : SUCCESS ===
ok
Attach volume to running VM, then reboot. ... === TestName: 
test_03_attached_volume_reboot_VM | Status : SUCCESS ===
ok
Detach volume from a running VM, then reboot. ... === TestName: 
test_04_detach_volume_reboot | Status : SUCCESS ===
ok
Detach volume from a stopped VM, then start. ... === TestName: 
test_05_detach_vol_stopped_VM_start | Status : SUCCESS ===
ok
Attach a volume to a stopped virtual machine, then start VM ... === 
TestName: test_06_attach_volume_to_stopped_VM | Status : SUCCESS ===
ok
Destroy and expunge VM with attached volume ... === TestName: 
test_07_destro

Re: [DISCUSS] Replacing the VR

[Will Stevens]

I feel like I have squashed this discussion with my potential approach to
handling this.  Maybe we should just pickup this discussion assuming I
didn't post that.  :P

Regarding the docs.  I have considered building a stubbed example network
plugin and then documenting how you would take that stub and build on it.
Would that be interesting?

*Will STEVENS*
Lead Developer

*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_

On Fri, Sep 23, 2016 at 12:15 AM, Murali Reddy 
wrote:

> Matthew,
>
> Please see https://cwiki.apache.org/confluence/display/CLOUDSTACK/
> Extending+CloudStack+Networking
>
> Thanks,
> Murali
>
>
>
>
>
> On 22/09/16, 11:23 PM, "Matthew Smart" 
> wrote:
>
> >Hey Murali,
> >
> >I have been reading through the API and other documentation to try to
> >get a basic understanding of the network service offering abstraction
> >methodology in CS. I have not dove into the code yet but before I did I
> >thought I would try a different approach.
> >
> >Imagine I were to come to this list and say that I have a network
> >offering that I sell and that I wanted to write whatever I needed to in
> >order to integrate it as an offering in CloudStack. Is there some
> >specific documentation and guidelines you would direct me to read in
> >order to gather the knowledge necessary to create a cloudstack
> >compatible interface for my product?
> >
> >I don't know the history but I see several products that have navigated
> >this process (Nuage, Nicira, ...etc) and am wondering how a new provider
> >would work with you guys to navigate that process. If this is too vague,
> >we can pretend my new offering is a hardware firewall device.
> >
> >My goal here is to gain an understanding of how CS interacts with third
> >party offerings underneath the hood. I have some thoughts (I think
> >inline with Will Steven's brain dump and diagram) but want to make sure
> >I am not suffering some misapprehensions about the architecture and,
> >short of tracing code, was not successful at finding the information I
> >needed to satisfy myself that I know how it is designed.
> >
> >Thanks,
> >
> >Matthew Smart
> >President
> >Smart Software Solutions Inc.
> >108 S Pierre St.
> >Pierre, SD 57501
> >
> >Phone: (605) 280-0383
> >Skype: msmart13
> >Email: msm...@smartsoftwareinc.com
> >
> >On 09/20/2016 04:54 AM, Murali Reddy wrote:
> >> Configuration management of network appliances particularly for Cloud
> and NFV scenarios is still evolving area. Programmability is the not the
> strength for even the most popular network operating systems like IOS,
> JunoS etc. So its not surprising why CloudStack integrates in a archaic way
> with stock linux for the VR.
> >>
> >> VR was never integral/hardcoded option in CloudStack. Its always been a
> plugin. CloudStack network orchestration is well abstracted and designed
> with vision to compose a network with different set of providers for
> different services. Yes that vision is not fully realised yet, and we don’t
> have true service function chains. That would be different discussion topic.
> >>
> >> I tend to agree with Simon, as alternate/interim option we can take
> hard look whats causing the problems with current VR integration.
> Personally, I think it would be easier we take a cue from configuration
> managers and network configuration solutions out there (for e.g promise
> theory based Cisco ACI) move to more declarative model of expressing
> desired state of network configuration. Infact current VR from 4.6,
> actually holds the desired state per service basis, seems to be in that
> direction.
> >>
> >> It does make sense to evaluate new appliances which can provide rich
> semantics (like programmable API, declarative configuration, versioning,
> commit/rollback etc), but will need significant engineering effort and time
> to stabilise. We may make same mistakes with integration of other appliance
> as well, if we fully don’t understand the nature of the current problems
> with CloudStack core and service provider interaction and current VR
> integration.
> >>
> >>
> >> On 16/09/16, 11:59 PM, "Simon Weller"  wrote:
> >>
> >>> I think our other option is to take a real look at what it would take
> to fix the VR. In my opinion, a lot of the problems are related to the
> monolithic python code base and the fact nothing is actually separated.
> >>>
> >>> Secondly, the python scripts (and bash scripts) don't use any
> established libraries to complete tasks and instead shell out and run
> commands that are both hard to track and hard to parse on return.
> >>>
> >>>
> >>> If we daemonized this, used a real api for Agent to VR communication,
> used common already existing libraries for the system service and network
> interactions and spent a bit of time separating out code into distinct
> modules, everything would behave a lot better.
> >>>
> >>>
> >>> The pain and suffering is due to years and years of patches and
>

[GitHub] cloudstack pull request #1659: CLOUDSTACK-9339 Virtual Routers don't handle ...

[abhinandanprateek]

Github user abhinandanprateek commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1659#discussion_r80615061
  
--- Diff: test/integration/component/test_multiple_public_interfaces.py ---
@@ -0,0 +1,1365 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+""" BVT tests for network services on public IP's from different public IP
+  range than that of associated source NAT IP of the network. Each IP 
associated
+  with network from a different public IP range results in a new public
+  interface on VR (eth3, eth4 etc) and iptable
+"""
+# Import Local Modules
+from marvin.codes import (FAILED, STATIC_NAT_RULE, LB_RULE,
+  NAT_RULE, PASS)
+from marvin.cloudstackTestCase import cloudstackTestCase
+from marvin.cloudstackException import CloudstackAPIException
+from marvin.cloudstackAPI import rebootRouter
+from marvin.sshClient import SshClient
+from marvin.lib.utils import cleanup_resources, get_process_status
+from marvin.lib.base import (Account,
+ VirtualMachine,
+ ServiceOffering,
+ NATRule,
+ PublicIPAddress,
+ StaticNATRule,
+ FireWallRule,
+ Network,
+ NetworkOffering,
+ LoadBalancerRule,
+ PublicIpRange,
+ Router,
+ VpcOffering,
+ VPC,
+ NetworkACL)
+from marvin.lib.common import (get_domain,
+   get_zone,
+   get_template,
+   list_hosts,
+   list_publicIP,
+   list_nat_rules,
+   list_routers,
+   list_virtual_machines,
+   list_lb_rules,
+   list_configurations,
+   verifyGuestTrafficPortGroups)
+from nose.plugins.attrib import attr
+from ddt import ddt, data
+# Import System modules
+import socket
+import time
+import logging
+
+_multiprocess_shared_ = True
+
+logger = logging.getLogger('TestNetworkOps')
+stream_handler = logging.StreamHandler()
+logger.setLevel(logging.DEBUG)
+logger.addHandler(stream_handler)
+
+class TestPortForwarding(cloudstackTestCase):
+
+@classmethod
+def setUpClass(cls):
+
+testClient = super(TestPortForwarding, cls).getClsTestClient()
+cls.apiclient = testClient.getApiClient()
+cls.services = testClient.getParsedTestDataConfig()
+cls.hypervisor = testClient.getHypervisorInfo()
+# Get Zone, Domain and templates
+cls.domain = get_domain(cls.apiclient)
+cls.zone = get_zone(cls.apiclient, testClient.getZoneForTests())
+cls.services["virtual_machine"]["zoneid"] = cls.zone.id
+cls.services["zoneid"] = cls.zone.id
+template = get_template(
+cls.apiclient,
+cls.zone.id,
+cls.services["ostype"]
+)
+if template == FAILED:
+assert False, "get_template() failed to return template with 
description %s" % cls.services[
+"ostype"]
+
+# Create an account, network, VM and IP addresses
+cls.account = Account.create(
+cls.apiclient,
+cls.services["account"],
+admin=True,
+domainid=cls.domain.id
+)
+cls.services["publiciprange"]["zoneid"] = cls.zone.id
+cls.service_offering = ServiceOffering.create(
+cls.apiclient,
+cls.services["service_offerings"][

[GitHub] cloudstack issue #1659: CLOUDSTACK-9339 Virtual Routers don't handle Multipl...

[abhinandanprateek]

Github user abhinandanprateek commented on the issue:

https://github.com/apache/cloudstack/pull/1659
  
@murali-reddy there is a potential to move some of the code into net 
utility classes, think about it.


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

[GitHub] cloudstack issue #1680: CLOUDSTACK-9498: VR CsFile search utility methods fa...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1680
  
@jburwell changed the existing marvin test to use password as 
"p@a#s=s.w_o-r+d", which will cover the all chars permitted for VPN user 
password


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

[GitHub] cloudstack issue #1681: CLOUDSTACK-9491: incorrect parsing of device list to...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1681
  
@jburwell function 'findRouterEthDeviceIndex' which is modified, is invoked 
when ever a new tier to VPC is added (virtual NIC is hot-plugged). Many VPC 
tests run againest the VMware environment will cover this scenario.


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

[GitHub] cloudstack issue #1681: CLOUDSTACK-9491: incorrect parsing of device list to...

[murali-reddy]

Github user murali-reddy commented on the issue:

https://github.com/apache/cloudstack/pull/1681
  
@blueorangutan test centos7 vmware55u3


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

[GitHub] cloudstack issue #1681: CLOUDSTACK-9491: incorrect parsing of device list to...

[blueorangutan]

Github user blueorangutan commented on the issue:

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


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