[GitHub] cloudstack pull request #1921: Dockerfile: Upgrade base distro to Ubuntu 16....

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1921: Dockerfile: Upgrade base distro to Ubuntu 16.04, fix...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1921
  
docker specific. merging.


---
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 #1920: Change the README link for event page to the current...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1920
  
+1 merging


---
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 #1920: Change the README link for event page to the ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1889: CLOUDSTACK-9718: Revamp the dropdown showing lists o...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1889
  
LGTM, did not test 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 #1741: Updated StrongSwan VPN Implementation

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
Ping, update on this? 


---
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 #1920: Change the README link for event page to the current...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1920
  
LGTM


---
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 #1921: Dockerfile: Upgrade base distro to Ubuntu 16.04, fix...

[rhtyd]

Github user rhtyd commented on the issue:

https://github.com/apache/cloudstack/pull/1921
  
LGTM, did not test 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 pull request #1921: Dockerfile: Upgrade base distro to Ubuntu 16....

[pdion891]

GitHub user pdion891 opened a pull request:

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

Dockerfile: Upgrade base distro to Ubuntu 16.04, fix support for JDK8

Fix current broken build introduce with JDK upgrade from #1888 of docker 
simulator because of missing dependencies and JDK8. This PR upgrade the distro 
to Ubuntu 16.04 and use default jdk version 8.

I've quickly test the build locally, no error in the UI and logs.

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

$ git pull https://github.com/pdion891/cloudstack dockerfile_ubuntu1604_jdk8

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

https://github.com/apache/cloudstack/pull/1921.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 #1921


commit 450d8d00fb5966c5cda8f2ed878f1b3add1adaf1
Author: Pierre-Luc Dion 
Date:   2017-01-31T01:35:10Z

Upgrade base distro to Ubuntu 16.04, fix support for JDK8, fix 
dependencies, should fix current broken build of docker simulator




---
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-docs-admin issue #41: 50% of the doc strings are translated into ...

[pdion891]

Github user pdion891 commented on the issue:

https://github.com/apache/cloudstack-docs-admin/pull/41
  
LGTM,  I'll merge this PR this week... 

Thanks a lot @lmrv for the translation ! 


---
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-docs-admin pull request #41: 50% of the doc strings are translate...

[pdion891]

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

https://github.com/apache/cloudstack-docs-admin/pull/41#discussion_r98378667
  
--- Diff: source/locale/fr/LC_MESSAGES/virtual_machines.po ---
@@ -0,0 +1,2188 @@
+# 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.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2016-08-22 13:55+0200\n"
+"PO-Revision-Date: \n"
+"Last-Translator: \n"
+"Language-Team: \n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=iso-8859-1\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: fr\n"
+"X-Generator: Poedit 1.8.11\n"
+
+#: ../../virtual_machines.rst:18
+msgid "Working with Virtual Machines"
+msgstr "Travailler avec les Machines Virtuelles"
+
+#: ../../virtual_machines.rst:21
+msgid "About Working with Virtual Machines"
+msgstr "A propos du travail avec les Machines Virtuelles"
+
+#: ../../virtual_machines.rst:23
+msgid ""
+"CloudStack provides administrators with complete control over the 
lifecycle of all "
+"guest VMs executing in the cloud. CloudStack provides several guest 
management "
+"operations for end users and administrators. VMs may be stopped, started, 
rebooted, "
+"and destroyed."
+msgstr ""
+"CloudStack fournit aux administrateurs le contr�le complet du cycle de 
vie de toutes "
+"les VM invit�es s'ex�cutant dans le cloud. CloudStack fournit 
plusieurs op�rations "
+"de gestion des invit�s aux utilisateurs finaux et aux administrateurs. 
Les VM "
+"peuvent �tre arr�t�es, d�marr�es, red�marr�es et 
d�truites."
+
+#: ../../virtual_machines.rst:28
+msgid ""
+"Guest VMs have a name and group. VM names and groups are opaque to 
CloudStack and "
+"are available for end users to organize their VMs. Each VM can have three 
names for "
+"use in different contexts. Only two of these names can be controlled by 
the user:"
+msgstr ""
+"Les VM invit�es ont un nom et un groupe. Les noms et groupes de VM sont 
opaques � "
+"CloudStack et sont disponibles pour que les utilisateurs finaux 
organisent leurs VM. "
+"Chaque VM peut avoir trois noms � utiliser dans diff�rents contextes. 
Seuls deux de "
+"ces noms peuvent �tre contr�l�s par l'utilisateur :"
+
+#: ../../virtual_machines.rst:33
+msgid ""
+"Instance name – a unique, immutable ID that is generated by CloudStack 
and can not "
+"be modified by the user. This name conforms to the requirements in IETF 
RFC 1123."
+msgstr ""
+"Nom de l'instance - un ID unique et non modifiable qui est g�n�r� 
par CloudStack et "
+"ne peut pas �tre modifi� par l'utilisateur. Ce nom est conforme aux 
exigences de la "
+"RFC 1123 de l'IETF."
+
+#: ../../virtual_machines.rst:37
+msgid ""
+"Display name – the name displayed in the CloudStack web UI. Can be set 
by the user. "
+"Defaults to instance name."
+msgstr ""
+"Nom affiché - le nom affiché dans l'interface web CloudStack. Peut 
être fixé par "
+"l'utilisateur. Prend par défaut le nom de l'instance."
+
+#: ../../virtual_machines.rst:40
+msgid ""
+"Name – host name that the DHCP server assigns to the VM. Can be set by 
the user. "
+"Defaults to instance name"
+msgstr ""
+"Nom - nom de machine que le serveur DHCP assigne à la VM. Peut être 
fixé par "
--- End diff --

@lmrv  is it normal to see weird character such as these?


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

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

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
There are some conflicts after the latest merge. Can you resolve them? 


---
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 #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implem...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #977: [4.10] CLOUDSTACK-8746: VM Snapshotting implementatio...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/977
  
great effort from everyone in terms of code, testing and discussion. 
Overall, all the comments are addressed and has test runs. I am merging this 
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.
---

Re: CCC Miami Sponsor: ShapeBlue

[Tutkowski, Mike]

If it helps, Raj, I downloaded the sponsorship prospectus for ApacheCon NA 2017 
and it says 700+ participants are expected.

On 1/29/17, 7:37 PM, "Rajesh Ramchandani"  
wrote:

Hi Will -


I was wondering if you could suggest what will be the attendance 
expectation at CCC? I am hoping it will be a lot more than the ApacheCon Europe 
last year. We would love to sponsor as long as we are able to rally our 
community members to attend. Thanks.


Raj



From: Will Stevens 
Sent: Sunday, January 29, 2017 10:05 AM
To: market...@cloudstack.apache.org; us...@cloudstack.apache.org; 
dev@cloudstack.apache.org
Subject: CCC Miami Sponsor: ShapeBlue

Please join me in welcoming ShapeBlue  as the
ShapeBlue - The CloudStack Company
www.shapeblue.com
Introduction Upgrading CloudStack can sometimes be a little daunting - but 
as the 5P's proverb goes - Proper Planning Prevents Poor Performance.



first official sponsor of the CloudStack Collaboration Conference in
Miami.  ShapeBlue has been a dedicated sponsor and Apache CloudStack
supporter and we are thrilled to have them on board for this event.

The CloudStack Collaboration Conference in Miami is being hosted by
ApacheCon and it is shaping up to be a great event.  We are all looking
forward to seeing you there.

If you would like more information about the event, please checkout the
event website: http://us.cloudstackcollab.org/
Apache CloudStack Collaboration Conference - 
USA
us.cloudstackcollab.org
Apache CloudStack Collaboration Conference hosted in Miami at ApacheCon.




If you are interested in sponsoring the event, please review the
sponsorship section: http://us.cloudstackcollab.org/#sponsors
Apache CloudStack Collaboration Conference - 
USA
us.cloudstackcollab.org
Apache CloudStack Collaboration Conference hosted in Miami at ApacheCon.




Thanks again for the support ShapeBlue and looking forward to seeing you at
the event.

Cheers,

Will Stevens
VP @ Apache CloudStack



DISCLAIMER
==
This e-mail may contain privileged and confidential information which is 
the property of Accelerite, a Persistent Systems business. It is intended only 
for the use of the individual or entity to which it is addressed. If you are 
not the intended recipient, you are not authorized to read, retain, copy, 
print, distribute or use this message. If you have received this communication 
in error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Re: [PROPOSAL] add native container orchestration service

[Rafael Weingärtner]

I have been following the discussion on this thread here. I agree with
everything that has been posted about the responsibility of
maintaining/supporting plugins that sometimes we feel are being left aside
and we do not know to what extent they are being used. However, as Will and
others highlighted, we need to work on new features/integrations;
otherwise, we may start losing market share to alternatives. In my opinion,
if the plugin/integration is well designed and coded/developed, I am more
than ok with it. And of course, let's not re-create something that already
exists. Of course, let's not re-create something that already exists;
integration is one thing re-create something that is already out there is
another.

I do not wish to cause a detour here; I only want to make a comment
regarding the ETSI and their specification for NFV (network functions)
management. Their idea is to manage the networking layer of the cloud. They
talk about managing NFVs (e.g. load balancers, virtual routers, firewalls
and others). ACS does that already (it deploys and manages these underlying
systems, am I mistaken?!). Their idea is to put this management process in
another layer out of the cloud orchestrator. I have seen their blueprints,
deployed and tested the system they have so far, and I am still a little
skeptical with the design (but that is probably only me). I have already
spoken with them, and they are open to integrate with other cloud computing
systems. They use OpenStack because most people working within the OPNFV
project comes from companies that use OpenStack, and their software right
now is quite tied to OpenStack. As a matter of fact, because of the lack of
contact with other communities, they are adapting the specs to OpenStack
needs, which seems a rather unusual process to do with the specification of
a standard. If some of you are interested, we could create a task force and
initiate contact and create a bridge from our project to theirs (by bridge
I mean open a channel of communications). If we do this, we will certainly
bring quite some attention to ACS (there a big telecommunication companies
behind OPNFV and ETSI ). I am working with NFVs management, and I would
much rather use ACS than OpenStack.


On Mon, Jan 30, 2017 at 2:54 AM, Murali Reddy 
wrote:

>
> I agree with some good views Will has shared and I also agree to the
> concerns raised by Wido and Eric. IMO we need balance of staying
> relevant/add new features vs stability of CloudStack and take corrective
> action if needed. We have two good examples for both. When SDN was hot
> technology CloudStack ended up with bunch of SDN controller integrations.
> Few years later, now CloudStack is carrying baggage with no maintainers for
> those plugins, with probably not many of CloudStack users needing overlays.
> On the other hand, other than attempt to liaison with ETSI for NFV no
> effort was done. OpenStack has become de-facto for NFV. Now for OpenStack,
> arguably NFV has become larger use case than cloud it self. I concur with
> Will’s point that with minimal viable solution that does not change the
> core of CloudStack, and can keep CloudStack relevant is worth to be taken
> in.
>
> Will,
>
> To your question of how different is from ShapeBlue’s container service,
> its design, implementation and API semantics etc remain same. ShapeBlue’s
> container service was true drop in plug-in to CloudStack, with this
> proposal I am trying to re-work to make it a core CloudStack pluggable
> service which is part of CloudStack.
>
> Key concepts that this proposal is trying to add
>
> - add notion of ‘container cluster’ as a first class entity in
> CloudStack. Which is bacially collection of other CloudStack resources
> (like VM’s, networks, public ip, network rules etc)
> - life cycle operation to manage ‘container cluster’ like create,
> delete, start, stop, scale-up, scale-down, heal etc
> - orchestrate container orchestrator control plane on top of
> provisioned resources
>
> At-least for k8s (which is what this proposal is targeting), integration
> with k8s is bare minimum. There are cloud-config scripts that automatically
> setup k8s cluster master and node VM’s. All CloudStack is doing in passing
> the cloud-config to the core OS VM’s as user data.
>
> Regards
> Murali Reddy
>
>
>
>
>
>
>
> On 29/01/17, 8:54 AM, "Will Stevens"  of wstev...@cloudops.com> wrote:
>
> >I agree that we need to be careful what we take on and own inside
> >CloudStack.  I feel like some of the plugins or integrations which we have
> >been "maintaining" may serve us better to abandon, but I feel like that is
> >a whole discussion on its own.
> >
> >In this case, I feel like there is a minimum viable solution which puts
> >CloudStack in a pretty good place to enable container orchestration.  For
> >example, one of the biggest challenges with K8S is the fact that it is
> >single tenant.  

[GitHub] cloudstack pull request #1920: Change the README link for event page to the ...

[rafaelweingartner]

GitHub user rafaelweingartner opened a pull request:

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

Change the README link for event page to the current ACS CCCs website

While reading the README file of Apache CloudStack repository on Github I 
noticed that we have a section called “News and Events”. This section was 
pointing to a website for conferences, which was not updated in years. I 
changed the link to send the users to http://cloudstackcollab.org/ hot site.
Moreover, I removed the reference for http://planet.apache.org/cloudstack; 
this system was shut down and is no longer available 
(http://markmail.org/message/wcdqncr6vr4lk6a7?q=planet%2Eapache%2Eorg#query:planet.apache.org+page:1+mid:6g76gvitxhlyee4n+state:results).

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

$ git pull https://github.com/rafaelweingartner/cloudstack 
fixConferenceLinks

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

https://github.com/apache/cloudstack/pull/1920.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 #1920






---
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 #1919: CLOUDSTACK-9763: set ssh public key when crea...

[serbaut]

GitHub user serbaut opened a pull request:

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

CLOUDSTACK-9763: set ssh public key when creating vm data



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

$ git pull https://github.com/serbaut/cloudstack CLOUDSTACK-9763

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

https://github.com/apache/cloudstack/pull/1919.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 #1919






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

RE: [PROPOSAL] add native container orchestration service

[Kishan Kavala]

Taking this abstraction one more level up, I propose we keep the cluster 
generic, and not just for container service. More so, because the proposal is 
to make it core cloudstack pluggable service.

With the proposed container orchestration service,
 - A notion of cluster is introduced, which is basically group of Vms, network 
rules etc
 
 Container service is not the only use-case which will benefit from this 
cluster. Any service which requires a bunch of Vms grouped can make use of this 
cluster.

 Any service which require the following can be supported by a generic 
framework, similar to network plugin framework.
 - Create group of Vms (ServiceCluster) and manage their life cycle 
 - Configure network to make the ServiceCluster functional (e.g. open required 
ports on all vms to for services to communicate)
 - Create network rules to make the control pane accessible (e.g. create 
PortForwarding rule to access k8s/PaaS dashboard)
 - Driven by cloud-config via userdata (e.g. config to download required 
binaries and start services on the Vms)
 - Support a purpose-built template (e.g. CoreOS)
 
This framework can be used by services like Container service, PaaS or 
DB-as-a-service .  I’ve been doing some prototypes on a similar kind of 
abstraction.

-Original Message-
From: Murali Reddy [mailto:murali.re...@shapeblue.com] 
Sent: Monday, January 30, 2017 1:24 PM
To: dev@cloudstack.apache.org
Subject: Re: [PROPOSAL] add native container orchestration service


I agree with some good views Will has shared and I also agree to the concerns 
raised by Wido and Eric. IMO we need balance of staying relevant/add new 
features vs stability of CloudStack and take corrective action if needed. We 
have two good examples for both. When SDN was hot technology CloudStack ended 
up with bunch of SDN controller integrations. Few years later, now CloudStack 
is carrying baggage with no maintainers for those plugins, with probably not 
many of CloudStack users needing overlays. On the other hand, other than 
attempt to liaison with ETSI for NFV no effort was done. OpenStack has become 
de-facto for NFV. Now for OpenStack, arguably NFV has become larger use case 
than cloud it self. I concur with Will’s point that with minimal viable 
solution that does not change the core of CloudStack, and can keep CloudStack 
relevant is worth to be taken in. 

Will,

To your question of how different is from ShapeBlue’s container service, its 
design, implementation and API semantics etc remain same. ShapeBlue’s container 
service was true drop in plug-in to CloudStack, with this proposal I am trying 
to re-work to make it a core CloudStack pluggable service which is part of 
CloudStack. 

Key concepts that this proposal is trying to add

- add notion of ‘container cluster’ as a first class entity in CloudStack. 
Which is bacially collection of other CloudStack resources (like VM’s, 
networks, public ip, network rules etc)
- life cycle operation to manage ‘container cluster’ like create, delete, 
start, stop, scale-up, scale-down, heal etc
- orchestrate container orchestrator control plane on top of provisioned 
resources

At-least for k8s (which is what this proposal is targeting), integration with 
k8s is bare minimum. There are cloud-config scripts that automatically setup 
k8s cluster master and node VM’s. All CloudStack is doing in passing the 
cloud-config to the core OS VM’s as user data.

Regards
Murali Reddy







On 29/01/17, 8:54 AM, "Will Stevens"  wrote:

>I agree that we need to be careful what we take on and own inside 
>CloudStack.  I feel like some of the plugins or integrations which we 
>have been "maintaining" may serve us better to abandon, but I feel like 
>that is a whole discussion on its own.
>
>In this case, I feel like there is a minimum viable solution which puts 
>CloudStack in a pretty good place to enable container orchestration.  
>For example, one of the biggest challenges with K8S is the fact that it 
>is single tenant.  CloudStack has good multi tenancy support and has 
>the ability to orchestrate the underlying infra quite well.  We will 
>have to be very careful not to try to own too deep into the K8S world 
>though, in my opinion.  We only want to be responsible for providing 
>the infra (and a way to bootstrap K8S ideally) and be able to scale the 
>infra, everything else should be owned by the K8S on top.  That is the 
>way I see it anyway, but please add your input.
>
>I think it is a liability to try to go too deep, for the same reasons 
>Wido and Erik have mentioned.  But I also think we need to take it 
>seriously because that train is moving and this may be a good 
>opportunity to stay relevant in a rapidly changing market.
>
>*Will STEVENS*
>Lead Developer
>
>
>
>On Sat, Jan 28, 2017 at 1:13 PM, Wido den Hollander  wrote:
>
>>
>> > Op 27 januari 2017 om 16:08 schreef 

Re: Current status of IPv6 in Basic Networking

[Wido den Hollander]

Hi,

Just wanted to inform people that my IPv6 code for KVM Basic Networking has 
been merged: 
https://github.com/apache/cloudstack/commit/f10c8bfe0c99a762c2606459413a47219614e775

This means that starting from CS 4.10 you can use IPv6 in KVM Instances and 
also provide Security Grouping in the same way as IPv4 can.

Much is still to be done, but this is a major step for IPv6 in CloudStack.

I will be working on documentation and some updated API calls so that you can 
enable IPv6 for existing networks without fiddling with the database manually.

Testing is very, very welcome! Please refer to the commit messages for now as 
documentation. I tried to be as descriptive as possible.

Wido

> Op 20 december 2016 om 21:48 schreef Wido den Hollander :
> 
> 
> Hi,
> 
> Just wanted to give an update on my IPv6 progress since my last [0] update.
> 
> The Wiki [1] still contains the most data about this, but the first PR [2] is 
> already open which should fix CLOUDSTACK-9359 [3].
> 
> When PR #1700 merges (I hope in to 4.10!) I will submit a second PR which 
> brings full Security Group support for IPv6 under KVM with Basic Networking.
> 
> The code [4] is already running on a private cloud at PCextreme and working 
> fine there. I really hope that code can also make it into 4.10 since that 
> will be a huge IPv6 step for CloudStack.
> 
> Afterwards I will be working on getting better IPv6 support for the SSVMs. 
> Main focus is still Basic Networking however. Anything additional is a good 
> side-effect.
> 
> I ask everybody to look at PR #1700 and give feedback. The sooner it merges, 
> the better.
> 
> Thanks!
> 
> Wido
> 
> [0]: 
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201610.mbox/%3C803597888.5548.1475520180772%40ox.pcextreme.nl%3E
> [1]: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+in+Basic+Networking
> [2]: https://github.com/apache/cloudstack/pull/1700
> [3]: https://issues.apache.org/jira/browse/CLOUDSTACK-9359
> [4]: 
> https://github.com/wido/cloudstack/commits/ipv6-basic-networking-secgroup-ports

Re: CCC Miami Update

[Wido den Hollander]

> Op 29 januari 2017 om 19:41 schreef Will Stevens :
> 
> 
> Hello Everyone,
> I am sure most of you are aware at this point that a CloudStack
> Collaboration Conference (CCC) is being hosted in Miami on May 16-18 by
> ApacheCon.
> 
> I urge you to consider joining us at this event.  Here are some of the
> important event details, but all the details can be found on our event
> website: *http://us.cloudstackcollab.org/ *
> 
> *Deadline for talk submissions:* *February 11th, 2017*
> *Accepted talk notifications:* *March 6th, 2017*
> *Schedule published on: **March 9th, 2017*
> 
> The event is being run as a collection of independently themed
> conferences.  Obviously, most of you will be specifically interested in the
> CloudStack Collaboration Conference, but your registration also gives you
> access to the other conference being run at the same time.  So far the
> other conferences include; 'Apache: Big Data', 'Apache: IoT', 'Flex Project
> Summit', 'Apache Traffic Server / Apache Traffic Control' and 'TomcatCon'.
> 
> The earlier you register, the more you save, so get your registration in
> early.
> 
> *Early Registration:* *until March 12, 2017*
> *Standard Registration:* *March 13, 2017 - April 16, 2017*
> *Late Registration:* *April 17, 2017 - Event Date*
> *Committer Registration:* Special pricing is available for active Apache
> Committers. Please contact the event organizers 
> for details.
> *Speaker Registration:* *One free registration is included with each
> accepted talk.*
> 
> If you submit a talk  and
> your talk is accepted, you will get one free registration per talk accepted.
> 

Great! With the recent merge of the IPv6 code for KVM Basic Networking I 
submitted a talk for IPv6 in Basic Networking.

This means I will be flying over to Miami in May :)

Wido

> We are still looking for event sponsors, so if you are interested in
> sponsoring the event, please review the sponsorship details
> .
> 
> If you have questions about anything, feel free to contact me directly and
> I will make sure you are connected with the right people.
> 
> Looking forward to seeing you all in Miami.
> 
> Cheers,
> 
> Will

[GitHub] cloudstack pull request #1910: CLOUDSTACK-9748:VPN Users search functionalit...

[Ashadeepa]

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

https://github.com/apache/cloudstack/pull/1910#discussion_r98422211
  
--- Diff: server/src/com/cloud/network/vpn/RemoteAccessVpnManagerImpl.java 
---
@@ -596,7 +597,7 @@ public void 
doInTransactionWithoutResult(TransactionStatus status) {
 
 
 sb.and("id", sb.entity().getId(), SearchCriteria.Op.EQ);
-sb.and("username", sb.entity().getUsername(), 
SearchCriteria.Op.EQ);
+sb.and("username", sb.entity().getUsername(), 
SearchCriteria.Op.LIKE);
--- End diff --

@ustcweizhou : Thanks but unfortunately, addOr & addAnd methods are now 
deprecated, so I avoided using the same.

Also, LIKE with work only when keyword is set. When only username is set,   
   `sc.setParameters("username", username); `
will get executed with the exact match i.e. same as how EQ will work!


---
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 #1910: CLOUDSTACK-9748:VPN Users search functionalit...

[ustcweizhou]

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

https://github.com/apache/cloudstack/pull/1910#discussion_r98412264
  
--- Diff: server/src/com/cloud/network/vpn/RemoteAccessVpnManagerImpl.java 
---
@@ -596,7 +597,7 @@ public void 
doInTransactionWithoutResult(TransactionStatus status) {
 
 
 sb.and("id", sb.entity().getId(), SearchCriteria.Op.EQ);
-sb.and("username", sb.entity().getUsername(), 
SearchCriteria.Op.EQ);
+sb.and("username", sb.entity().getUsername(), 
SearchCriteria.Op.LIKE);
--- End diff --

I vote EQ instead LIKE here.
you may add new rules here in the next part, for example.

+if (keyword != null) {
+final SearchCriteria ssc = 
_vpnUsersDao.createSearchCriteria();
+ssc.addOr("username", SearchCriteria.Op.LIKE, "%" + keyword + 
"%");
+ssc.addOr("state", SearchCriteria.Op.EQ, "%" + keyword + "%");
+sc.addAnd("username", SearchCriteria.Op.SC, ssc);
+}




---
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 #1918: Management Server UI (VM statistics page) CPU...

[jayakarteek]

GitHub user jayakarteek opened a pull request:

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

Management Server UI (VM statistics page) CPU Utilized value is incorrect.

VMware CPU Utilised  value is in Mhz , in MS value is displayed directly.
If CPU utilised is 500Mhz,  UI value is displayed as 500 %

Planned to restrict changes in resource layer VmwareResource.java, but cpu 
allocated to VM by VMware is not same as  allocated in the service offering.

If CPU limit flag is set to false in  service offerings  the Allocated CPU 
can go beyond what is assigned.
So picking actual user assigned Total CPU from database for calculating 
percentage.  
It is expected that percentage would go beyond 100 percent.

 so changes are made in UserVmJoinDaoImpl.java 


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

$ git pull https://github.com/jayakarteek/cloudstack cloudstack-9762

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

https://github.com/apache/cloudstack/pull/1918.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 #1918


commit 58d721603300b236bded82147363a06e80ecf67a
Author: Jayakarteek Vasana 
Date:   2017-01-30T09:06:03Z

 Bug fix for CLOUDSTACK-9762   Management Server UI (VM statistics page) 
CPU Utilized value is incorrect




---
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.
---