semvec/pypi-packages huggingface dataset:
tripleo-quickstart-extras 2.1.1
Extend tripleo-quickstart's abilities to deploy and test TripleO

========================
Team and repository tags
========================

.. image:: https://governance.openstack.org/tc/badges/tripleo-quickstart-extras.svg
    :target: https://governance.openstack.org/tc/reference/tags/index.html

.. Change things from this point on

==================================
Extra roles for tripleo-quickstart
==================================

These Ansible role are extending the functionality of tripleo-quickstart to do
end-to-end deployment and testing of TripleO.

The documentation of each role is located in the individual role folders, and
general usage information is in the `tripleo-quickstart documentation
<https://docs.openstack.org/tripleo-quickstart/latest/>`_.
mutextree 1.2.3
Protect tree-like resources

mutextree
==========
|black|

To protect tree-like resources:

.. image:: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-voc.png

Nodes have to be represented by their fully qualified name.
For instance, the node D is represented by [A, B, D]:

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-qualified-name.png

The algorithm to lock a node is the following:

1. We lock the parent nodes in order:

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-step1.png

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-step2.png

2. Then we check that no child node is already locked:

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-step3.png

3. We lock the wanted node

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-step4.png

4. We release all the parent locks that are no longer usefull.

.. image :: https://raw.githubusercontent.com/SewanDevs/mutextree/master-github/images/mutextree-step5.png


Interface targeted to be exactly like threading.Lock_.

.. _threading.Lock : <http://docs.python.org/2/library/threading.html#threading.Lock>`

The mutex tree is actually designed to use redis and python-redis-lock but the locking backend may be changed.


Usage
------------

To use mutextree with the redis locks back end, simply instanciate a redis client and create your lock.
The redis client should be strict and decode responses itself.

.. code-block:: python

    import redis
    from mutextree import RedisLockBackend, TreeLock

    redis_client = redis.StrictRedis(decode_responses=True)
    redis_lock_backend = RedisLockBackend(redis_client)
    lock = TreeLock(redis_lock_backend, ["nodeA"], expire=10, timeout=10, id=1)
    try:
        lock.acquire()
        # do things
    finally:
        lock.release()


You can use it as a context manager or a decorator:

.. code-block:: python

    import redis
    from mutextree import RedisLockBackend, TreeLock, tree_lock

    redis_client = redis.StrictRedis(decode_responses=True)
    redis_lock_backend = RedisLockBackend(redis_client)

    with TreeLock(redis_lock_backend, ["nodeA"], expire=10):
        # do things
        pass
        # release will be automatically called

    # Or with a decorator
    @tree_lock(redis_lock_backend, ["nodeA"], expire=10)
    def protected_function():
        # do things
        pass
        # release will be automatically called


Lock has the same basic interface as threading.Lock() with some more methods: acquire, release, refresh.


Tests
------

Tests should be run under python 2.7 and python 3.6 to tests everything

.. code-block:: console

    $ pip install tox
    $ tox -e py27,py36

Coverage reports will be the merge of the coverage for py27 and py36.

.. |black| image:: https://img.shields.io/badge/code%20style-black-000000.svg
   :target: https://github.com/ambv/black
tripleo-quickstart 2.1.1
tripleo-quickstart - Making it easy to get started with tripleo

========================
Team and repository tags
========================

.. image:: https://governance.openstack.org/tc/badges/tripleo-quickstart.svg
    :target: https://governance.openstack.org/tc/reference/tags/index.html

.. Change things from this point on

tripleo-quickstart
==================

An up-to-date HTML version is available on docs.openstack.org_.

.. _docs.openstack.org: https://docs.openstack.org/tripleo-quickstart/latest/

Release notes for the project can be found at:
https://docs.openstack.org/releasenotes/tripleo-quickstart/

One of the barriers to entry for trying out TripleO and its derivatives has
been the relative difficulty in getting an environment up quickly.

This set of ansible roles is meant to help.

Quickstart's default deployment method uses a physical machine, which is
referred to as ``$VIRTHOST`` throughout this documentation. On this physical
machine Quickstart sets up multiple virtual machines (VMs) and virtual networks
using libvirt.

One of the VMs is set up as **undercloud**, an all-in-one OpenStack cloud used
by system administrators to deploy the **overcloud**, the end-user facing
OpenStack installation, usually consisting of multiple VMs.

You will need a ``$VIRTHOST`` with at least **16 GB** of RAM, preferably **32
GB**, and you must be able to ``ssh`` to the virthost machine as root without a
password from the machine running ansible.  Currently the virthost machine must
be running a recent Red Hat-based Linux distribution (CentOS 7.x, RHEL 7.x).
Other distributions could work but will not be supported with out CI validation.

..  note::
    Running quickstart.sh commands as root is not suggested or supported.

The SSH server on your ``$VIRTHOST`` must be accessible via public keys for
both the root and stack users.

A quick way to test that root to your virthost machine is ready to rock is::

    ssh root@$VIRTHOST uname -a

The ``stack`` user is not added until the quickstart deploy runs, so this cannot
be tested in advance.  However, if you lock down on a per-user basis, ensure
``AllowUsers`` includes ``stack``.

Timeouts can be an issue if the SSH server is configured to disconnect users
after periods of inactivity.  This can be addressed for example by::

    ClientAliveInterval 120
    ClientAliveCountMax 720

The quickstart defaults are meant to "just work", so it is as easy as
downloading and running the ``quickstart.sh`` script.

Copyright
---------

Copyright 2015-2016 Red Hat, Inc.

Licensed 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.
wagtailmarkdownblock 0.3.3
Wagtail Markdown Block provides PrismJS Markdown conversion in Wagtail.

# Wagtail Markdown Block

**PLEASE NOTE:** Future development on this package will be limited, since most of the features are now included in the new Draftail editor available in Wagtail. Thank you to everyone who contributed!

Markdown blocks for Wagtail Streamfields.

This Django app uses the [SimpleMDE](https://simplemde.com/) Markdown editor in the Wagtail Admin and the website.

## Example Usage

    from wagtailmarkdownblock.blocks import MarkdownBlock

    class ContentStreamBlock(StreamBlock):
        paragraph = RichTextBlock()
        heading = TextBlock()
        code = MarkdownBlock()

## Contributors

* Timothy Allen (https://github.com/FlipperPA)
* Milton Lenis (https://github.com/MiltonLn)
* Mathias Picker (https://github.com/mathiasp)
* Tobias Ernst (https://github.com/to-bee)