[OpenStack] OpenStack Foundation Board Election 2016

It’s a well-followed process across multiple open source projects to announce candidacy over public mailing lists or blogs. Following up on the OpenStack Foundation Board Election process from last year I really liked the way Sean Roberts start of the blog for the candidature. “OpenStack is maturing. It’s 5+ years old now.” No doubt OpenStack is maturing in terms of projects being adopted, skills, integrations, vendors.

Being a contributor to the community, I feel whether its contributions that make eligible to consider for the candidacy or just promotions; whether people vote for people who promote only during elections or to people who they see active in the community.

Year-on-year we see people nominated from a variety of demographics, organizations. As a contributor,  I will see what how many patchsets the person has sent upstream, is he active across ML discussions, can he justify/answer/defend if someone asks him an OpenStack question from the audience in a meetup/event? At lease one of it should have a favourable answer to vote.

If you’re contributing to OpenStack, take some time before you vote to judge the candidates; judge on merit rather than promotion. I did the same.

Let’s make the community stronger.

[CentOS] Installing Go 1.5.2 on CentOS7

A quick guide on how to install the Go 1.5.2 on a CentOS 7 server.

Start by grabbing the latest 1.5.2 release for CentOS7 the download  pages.

$ cd /tmp
$ wget https://storage.googleapis.com/golang/go1.5.2.linux-amd64.tar.gz

Extract the binary files to /usr/local/go.

$ tar -C /usr/local -xzf /tmp/go1.5.2.linux-amd64.tar.gz

For easy access, symlink your installed binaries in /usr/local/go to /use/local/bin, which should be in your default $PATH in your shell.

$ echo $PATH
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

Create soft links for Go binaries

$ ln -s /usr/local/go/bin/go /usr/local/bin/go
$ ln -s /usr/local/go/bin/godoc /usr/local/bin/godoc
$ ln -s /usr/local/go/bin/gofmt /usr/local/bin/gofmt

Alternatively, add the /usr/local/go/bin directory to your $PATH. Add the following line to your ~/.profile file.

export PATH=$PATH:/usr/local/go/bin

You now have the working go binary for version 1.5.2$ go version

$ go version
go version go1.5.2 linux/amd64

Announcement : OpenStack Online Meetup

Greetings,
It gives me immense pleasure to announce a well deserved Online Meetup place for all OpenStack community members in India. With the ever growing participation to use, evaluate and contribute to OpenStack, the community in India is growing at a very fast pace. With the large geographical diversity of physical meetup places (and travel costs involved for attending meetups), there needs a mechanism for all to collaborate, share our ideas and a place to look at if we miss anything with all the real world complexities involved.
I hereby invite everyone interested to share any tini-tiny bit they want to community members to know to join us at the URL provided below with their interest and we will make sure there will be event scheduled for you to collaborate with those who are interested.
Feel free to shoot direct mail to the mail with any suggesions/queries you might have.
We all #love #OpenStack. Lets make the community stronger.

[OpenStack][RDO] Liberty Test-Day

RDO-Test-Day-Liberty

Tested Setups

Pre-req : CentOS 7 VM/BM

$ sudo su –

# yum install wget deltarpm -y

# cd /etc/yum.repos.d/

# rm -f delorean-deps.repo delorean.repo

# sudo wget http://trunk.rdoproject.org/centos7-liberty/delorean-deps.repo

# sudo wget http://trunk.rdoproject.org/centos7-liberty/current-passed-ci/delorean.repo

# yum update -y

# yum install vim openstack-packstack -y

 

[1] All-In-One – Glance-localfs, Cinder-lvm 

Generate an answer file with following command

packstack –gen-answer-file=answers.txt

Update the generated answer file with similar contents as example-answer-file

Note: Do not copy-paste, if you do, remember to update X.X.X.X with your system IP address

[2]  All-In-One – Glance-swift, Cinder-lvm

packstack –gen-answer-file=answers.txt

Update the generated answer file with similar contents as example-answer-file

Note: Do not copy-paste, if you do, remember to update X.X.X.X with your system IP address

[3] All-In-One – Glance-localfs, Cinder-glusterfs

packstack –gen-answer-file=answers.txt

Update the generated answer file with similar contents as example-answer-file

Note: Do not copy-paste, if you do, remember to update X.X.X.X with your system IP address

 

[4] Ceilometer: All-in-One w/ Neutron Networking, Heat

packstack –gen-answer-file=answers.txt

Update the generated answer file with similar contents as example-answer-file

Note: Do not copy-paste, if you do, remember to update X.X.X.X with your system IP address

[OpenStack] How to set up DevStack with Ceilometer

Prerequisites:
– DevStack setup requires to have 1 VM/ BM machine with internet connectivity.
– Setup a fresh supported Linux installation. (Ubuntu/Fedora/CentOs)
– Install Git

Steps
1. Clone devstack from devstack.

$git clone https://github.com/openstack-dev/devstack.git

2. Clone devstack localrc for ceilometer from devstack-ceilometer

$git clone https://github.com/svashu/devstack-ceilometer

3. Copy the localrc from devstack-ceilometer to devstack

$cp devstack-ceilometer/localrc devstack/localrc

4. Modify the devstack/localrc for IP and password modifications

5. Deploy your Devstack

$cd devstack && ./stack.sh

After completion of the sript you will get following message

Horizon is now available at http://X.X.X.X/
Keystone is serving at http://X.X.X.X:5000/v2.0/
Examples on using novaclient command line is in exercise.sh
The default users are: admin and demo
The password: xxxxxxx
This is your host ip: X.X.X.X

Source credentials required for executing commands

For demo user

$source accr/demo/demo

For admin user

$source accr/admin/admin

Attending FUDCon, here’s my wishlist, whats yours?

FUDCon is the Fedora Users and Developers Conference, a major free software event held in various regions around the world, usually annually per region. FUDCon is a mix of sessions. There are talks that range from technology introductions to deep dives, hands-on workshops, BoFs where like-minded people get together to discuss a project or technology and hackfests where contributors work on specific initiatives. Topics include infrastructure, feature development, community building, general management and governance, marketing, testing and QA, packaging, etc. FUDCon is always free to attend for anyone in the world.

See more details about FUDCon Pune 2015

Venue : MIT College of Engineering

Schedule: Friday, June 26, 2015 – 09:00 to Sunday, June 28, 2015 – 17:30

I am attending and presenting at FUDCon, here’s my schedule,

Introduction to Software Defined Storage – Ceph and GlusterFS
Geo-Replication and Disaster Recovery : GlusterFS
Openstack on Fedora, Fedora on Openstack: An Introduction to cloud IaaS
Fedmsg: The message bus of Fedora Infrastructure
Introduction to CentOS Cloud SIG
Contributing to OpenStack 101
Fedora Atomic
Hands-On Kubernetes
Getting Started with IOT development using Fedora on ARM
Orchestration of Docker containers using Openshift v3 and Kubernetes

Find the complete schedule of talks and workshops here

See you at FUDCon 🙂 Cheers!

[OpenStack] Install and Configure RDO-Juno with GlusterFS

Prerequisites:
– DevStack setup requires to have 1 VM/ BM machine with internet connectivity.
– For Gluster backends have VM(s) with atleast 30-40GB disk space
– Setup a fresh supported Linux installation. (CentOS/Fedora)

Setup and Configure Gluster

Steps to Setup Gluster
Steps to Configure Gluster

RDO Installation

In RDO QuickStart Guide,

Follow the Step 0: Prerequisites, as defined

In Step 1: Software Repositories after doing

sudo yum update -y

instead of installing rdo-release.rpm install do

sudo yum install -y https://rdoproject.org/repos/openstack-juno/rdo-release-juno.rpm

Check the rdo-release configured for packages is OpenStack-Juno

# cat /etc/yum.repos.d/rdo-release.repo
[openstack-juno]
name=OpenStack Juno Repositor
baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RDO-Juno

Follow instructions in Step 2: Install Packstack Installer

Generate answer-file for packstack installer with following command,

#packstack –gen-answer-file

You will get the packstack answerfile will be created in home directory of the user you are invoking packstack with. In my case it was in /root with prefix packstack-answers-xxx.txt, where xxx=timestamp.

Edit the answerfile for following details,

Set CONFIG_CINDER_BACKEND=gluster

Update CONFIG_CINDER_GLUSTER_MOUNTS with comma saperated list of gluster volumes in the format ip-address:/vol-name, domain:/vol-name

Run packstack installer with answer-file

#packstack –answer-file=/root/packstack-answers-xxx.txt

(Replace file name with your generated file)

Verify if gluster is configured as backend for your openstack deployment

# source keystonerc_admin
# cinder service-list
+——————+————————-+——+———+——-+—————————-+—————–+
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+——————+————————-+——+———+——-+—————————-+—————–+
| cinder-backup | centos-rdo-juno | nova | enabled | up | 2015-06-22T12:19:21.000000 | None |
| cinder-scheduler | centos-rdo-juno | nova | enabled | up | 2015-06-22T12:19:20.000000 | None |
| cinder-volume | centos-rdo-juno@gluster | nova | enabled | up | 2015-06-22T12:19:21.000000 | None |
+——————+————————-+——+———+——-+—————————-+—————–+

[OpenStack] Installing OpenStack Juno with RDO

Installing OpenStack Juno with RDO

If I visit the RDO QuickStart Guide, I did not find any instructions to deploy OpenStack Juno version.

I did some digging and tried to install OpenStack Juno with RDO,

Follow the Step 0: Prerequisites, as defined
In Step 1: Software Repositories after doing sudo yum update -y instead of installing rdo-release.rpm install do

sudo yum install -y https://rdoproject.org/repos/openstack-juno/rdo-release-juno.rpm

Check the rdo-release configured for packages is OpenStack-Juno

# cat /etc/yum.repos.d/rdo-release.repo
[openstack-juno]
name=OpenStack Juno Repository
baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-juno/epel-7/
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RDO-Juno

Follow the same procedure for rest installation.

Tip: If you get any failures for package installation or service not getting started, the packstack answerfile will be created in home directory of the user you are invoking packstack with. In my case it was in /root with prefix packstack-answers-xxx.txt. Do not run packstack all-in-one again.

Try running below command if you get any failure. I got failure for iptables service, but got successful installation.

#packstack –answer-file=/root/packstack-answers-20150622-091753.txt

National Institute of Standards and Technology (NIST) Cloud Computing Forum & Workshop VIII

NIST Workshop

As a part of NIST Cloud Computing Program, NIST will host its eighth Cloud Computing Forum and Workshop on July 7-10, 2015. The format will be a 4-day event with the first day focusing on Cloud Standards (organized by ISO/IEC JTC1 SC38) followed by 3-days of Talks and Panels centered on specific areas of research and development in the cloud environment.

The event will cover:

Current State of Cloud Computing Standards
This topic puts the spotlight on the active and productive field of cloud computing standards. NIST SP 500-293 (Technology Roadmap) and NIST SP 500-291 (Standards Roadmap) identified the need for cloud computing standards and identified initial efforts in developing such standards. Now Standards Development Organizations (SDOs), trade consortiums, academia, and other organizations are all working on cloud computing standards to address the cloud computing community’s needs. This topic highlights and showcases completed standards, standards in development, and opportunities for collaboration on future additional standards.

Progress on the NIST SP 500-293: 10 High Level Requirements for Cloud Adoption
In July, 2011 NIST released its first draft NIST SP 500-293: Technology Roadmap document that identified 10 high level requirements that were impeding wide spread adoption of cloud computing by the community. These requirements address the priorities in security, interoperability and portability. For the past several years industry has been working on addressing many of those) requirements and it is time to see which been addressed and which still need some work. As there are no fixed criteria to identify absolute success for any of the 10 requirements, this topic will highlight presentations showing either how specific requirements have been addressed or which still need some work. A full listing of the 10 requirements, which cover cloud security, cloud services, technical language for SLAs, cloud metrics and research, in the final version from October 2014, can be found here.

Cloud Forensics
As cloud computing becomes ever more widely used, there is an increasing need to perform digital forensics in the cloud to support criminal or civil investigations or business processes, to investigate cyberattacks and data breaches, or to proactively support security and forensics cloud-based applications. In June, 2014 NIST released the draft NIST Interagency Report 8006 NIST Cloud Computing Forensic Science Challenges. This document identifies 65 challenges facing cloud forensic investigators. During our event, we will focus on cloud forensic architectures in addition to eight of the highest priority challenges identified in the NISTIR 8006: Root of trust, E-discovery, Deletion in the cloud, Lack of transparency, Timestamp synchronization, Use of metadata, Multiple venues and geolocations, and Data integrity and evidence preservation. A description of these challenges can be found here.

Cloud Computing: Customers and Government
The US Government has a large stake in the field of cloud computing and continues to seek out new solutions for operationalizing the cloud computing model in order to serve the citizenry. Other governments have also seen the value in cloud computing and the economic, technological and societal benefit that cloud computing brings to the table. Debates and challenges still persist for cloud customers around the procurement, contracting and the convergence of technological capability and policy issues. This topic will illustrate some these challenges and successes of creative outcomes in various government agencies and customers

The CFP and shortlisting of Talks related to specific areas has just been completed. Here’s the final agenda and speakers bio

[OpenStack] OpenStack oslo packages not available in devstack? Here’s how you should do it

Prerequisites:
– DevStack setup requires to have 1 VM/ BM machine with internet connectivity.
– Setup a fresh supported Linux installation. (Ubuntu/Fedora/CentOs)
– Install Git

Steps
1. Clone devstack from devstack.

$git clone https://github.com/openstack-dev/devstack.git

2. Create your local.conf as per requirement

2. Add following line in your local.conf

LIBS_FROM_GIT = cliff,debtcollector,oslo.concurrency,oslo.config,oslo.context,oslo.db,oslo.i18n,oslo.log,oslo.messaging,oslo.middleware,oslo.policy,oslo.rootwrap,oslo.serialization,oslo.utils,oslo.versionedobjects,oslo.vmware,pycadf,stevedore,taskflow,tooz,pbr

4. Deploy your Devstack

$cd devstack && ./stack.sh

After completion of the sript you will get following message

Horizon is now available at http://X.X.X.X/
Keystone is serving at http://X.X.X.X:5000/v2.0/
Examples on using novaclient command line is in exercise.sh
The default users are: admin and demo
The password: xxxxxxx
This is your host ip: X.X.X.X

Locate if your oslo packages are cloned from git

$ls /opt/stack

Source credentials required for executing commands

For demo user

$source accr/demo/demo

For admin user

$source accr/admin/admin