vkmc

################################################################
# This local.conf sets up Devstack with manila enabling the LVM
# driver which operates in driver_handles_share_services=False
# mode
################################################################

[[local|localrc]]
ADMIN_PASSWORD=secret
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD

vkmc

# delete evicted pods from all namespaces

kubectl get pods --all-namespaces | grep Evicted | awk '{print $2 " --namespace=" $1}' | xargs -n 2 -d '\n' bash -c 'kubectl delete pod $0 $1'

vkmc

- tempest init <some-name> (this will create an environment).
This is not actually needed (I noticed later) since Devstack set ups the Tempest environment
for you in /opt/stack/tempest
- tox -e genconfig. This will generate the config file for you and store it under etc/.
Again, not needed for Devstack since it does it automatically and you can find the config
file already generated in etc/. The only thing you need to modify there is the Manila
section (copy paste the one you are using, which I assume is what we have on the gate, and that must be fine).
- Check that tempest is seeing the plugin.
For what I saw, you specified enable_plugin manila_tempest_plugin in local.conf,
and that won't work because there is no Devstack plugin for manila_tempest_test project.

vkmc

[[local|localrc]]

DEST=/opt/stack
LOGFILE=$DEST/logs/devstacklog.txt
LOG_COLOR=False

ADMIN_PASSWORD=secret
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD

vkmc

[[local|localrc]]

# auth
ADMIN_PASSWORD=nomoresecret
DATABASE_PASSWORD=stackdb
RABBIT_PASSWORD=stackqueue
SERVICE_PASSWORD=$ADMIN_PASSWORD

# enable logging
LOGFILE=/opt/stack/logs/stack.sh.log

vkmc

[[local|localrc]]

# auth
ADMIN_PASSWORD=nomoresecret
DATABASE_PASSWORD=stackdb
RABBIT_PASSWORD=stackqueue
SERVICE_PASSWORD=$ADMIN_PASSWORD

# manila
enable_plugin manila https://opendev.org/openstack/manila

vkmc

[[local|localrc]]
ADMIN_PASSWORD=secret
DATABASE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=$ADMIN_PASSWORD
SERVICE_PASSWORD=$ADMIN_PASSWORD
DEST=/opt/stack
DATA_DIR=/opt/stack/data
LOGFILE=/opt/stack/devstacklog.txt

vkmc

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

vkmc

https://wiki.gnome.org/OutreachProgramForWomen/2013/JanuaryApril
Jan-Apr 2013

Laura Alves da Quinta (ladquin), Buenos Aires, Argentina - Documentation - Anne Gentle
Anita Kuno (anteaya), Haliburton, Ontario, Canada - Python Clients - Iccha Sethi
Victoria Martínez de la Cruz (vkmc), Bahía Blanca, Argentina - Horizon's Workflows - Julie Pichon

https://wiki.gnome.org/OutreachProgramForWomen/2013/JuneSeptember
June-September 2013

vkmc

The term "open source" in the software industry is no longer a novelty: open source, as we know it, has been around for more than 20 years now [1] and it describes the way in which several companies have been working together for the purpose of creating well-built, reliable and adaptable software.

It's true that, sometimes, open source may appear as something new and something that maybe your company cannot trust on. In other words, how can you do business relying in software that has been built by hundreds of individuals and in which anyone can come and submit a change? It just feels... risky.

In this post today we will try to clear this out, sharing how open source organizations work, from both the technical and the organizational stand points, and also we will share some tips on how you can also contribute to open source.

Open source communities

Open source code