[opnfv-tech-discuss] Auto Project Meeting 02/19/2018 - Auto - OPNFV Wiki

[Tina Tsou]

Dear all,

Agenda for Auto Project weekly meeting for 6am 02/19 PT is posted.

https://wiki.opnfv.org/pages/viewpage.action?pageId=16941253

Talk to you soon.


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and Arm pod at UNH

[SULLIVAN, BRYAN L (BRYAN L)]

Sofia,

If there’s anything I’ve done in the Models project work referenced below that 
may be useful to you, let me know and I can provide any support you need. Helm 
is deployed as part of this stack, and used to deploy other stack components 
including:

  *   Ceph-docker as SDS backend: 
ceph-helm.sh
 *   Currently using Helm as I investigate other options e.g. Cloudify
  *   Various demo Apps to verify k8s + PVC (via Ceph) operation
  *   The VES components are also deployable via Helm, since the Cloudify 
blueprints just wrap 
k8s charts in a TOSCA blueprint with a small amount of Cloudify-specific 
attributes.

The Helm install and demo use scripts are in 
helm-tools.sh.
 This script is called in 
demo_deploy.sh
 after the base cluster (k8s-master+CNI+k8s-workers) is deployed.

The advantage of using Cloudify (or the ONAP OOM project, which is where this 
work is heading) for deploying stack components is that we don’t need to use 
Helm directly (e.g. via invocation over SSH) on the k8s cluster, rather can 
invoke chart operations via the Cloudify API. This meets one design goal which 
is to minimize any operations that must be performed over SSH, for 
security/reliability reasons, e.g. operations over APIs have inherently smaller 
attack surfaces. It also means that unless there is a specific stack deployment 
need for Helm, it doesn’t have to be installed, further improving 
security/reliability (any untested/unused code should not be deployed).

Thanks,
Bryan Sullivan | AT

From: Sofia Enriquez [mailto:lsofia.enriq...@gmail.com]
Sent: Friday, February 16, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L) 
Cc: gerard.d...@wipro.com; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Auto] VNFs and ONAP setup for Kubernetes and 
Arm pod at UNH

Maybe this may interest you. It's not specific to ARM, but CONTAINER4NFV 
project is working on a Clearwater implementation with K8s[0] and Helm[1]. Helm 
deployment will be Istio compatible. I wrote some documentation about it [2].

Best Regards,
Sofia

[0]: 
https://gerrit.opnfv.org/gerrit/#/c/50467/
[1]: 
https://gerrit.opnfv.org/gerrit/#/c/51603/
[2]: 
https://github.com/opnfv/container4nfv/blob/master/docs/release/userguide/clearwater-project.rst

2018-02-16 17:36 GMT-03:00 SULLIVAN, BRYAN L (BRYAN L) 
>:
Not specific to ARM, but I have implemented clearwater-docker as part of the 
Models kubernetes demo deploy, which includes a full-stack k8s cluster 
deployment, ending with clearwater-docker deployment and test. See 
https://github.com/opnfv/models/tree/master/tools/kubernetes
 for an overview of the process. The clearwater-docker deployment script is at 
k8s-cloudify-clearwater.sh
 (note this currently uses kubectl to deploy… I am working on wrapping the 
charts in TOSCA so I can use cloudify-kubernetes to deploy it, over the 
cloudify-manager API).

Note that the models scripts use clearwater-docker containers built for this 
test. It may be possible to build them for ARM platforms, after which the rest 
of the deploy process should work as scripted. The build scripts are 

[opnfv-tech-discuss] [OPNFV status] Confirm your subscription

[noreply]

OPNFV - Notification Subscription Confirmation

Thanks for subscribing to OPNFV status updates. You're almost done - we just 
need to confirm your subscription.

In order to activate your subscription, please go to the following URL:

http://status.opnfv.org/confirm/3Hr2BIgVRjViAn75


  --
  OPNFV Status: http://status.opnfv.org
To unsubscribe: http://status.opnfv.org/?unsubscribe=vfyld3fzkv6z___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [OPNFV status] Subscription removed

[noreply]

We're sorry to see you go. This email confirms that you have unsubscribed from 
OPNFV status updates.

You can resubscribe at any time by visiting http://status.opnfv.org.___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss