Commit 04059692 authored by Christos Stavrakakis's avatar Christos Stavrakakis
Browse files

Merge branch 'release-0.13' into develop

Conflicts:
	snf-astakos-app/astakos/im/messages.py
parents 7cdeced6 0efdd753
Copyright (C) 2010, 2011, 2012 GRNET S.A. All rights reserved.
Copyright (C) 2010, 2011, 2012, 2013 GRNET S.A. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
......@@ -16,7 +16,7 @@ conditions are met:
THIS SOFTWARE IS PROVIDED BY GRNET S.A. ``AS IS'' AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL GRNET S.A OR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL GRNET S.A. OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
......
.. _Changelog:
Unified Changelog file for Synnefo versions >= 0.13
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Since v0.13 most of the Synnefo components have been merged into a single
repository and have aligned versions.
.. _Changelog-0.13:
v0.13
=====
Release Date: UNRELEASED
In v0.13 the code was very heavily refactored for increased uniformity since
most of the Synnefo components have been merged into a single repository. Thus,
**just for this version** we will not document a complete Changelog (features,
fixes, improvements, issues, setting changes), but rather just copy from the
`NEWS` file with minor additions wherever needed.
Synnefo-wide
------------
* Support for pooling throughout Synnefo
* Pooled Django DB connections, Pithos backend connections, HTTP
connections using single `objpool` package
* Improved management commands
* Unified codebase for output of tables in JSON, CSV
* Bring most of Synnefo code inside a single, unified repository
* support automatic Python and Debian package builds for individual commits
* with automatic version generation
* Overhauling of Synnefo settings: renames and refactoring, for increased
uniformity (in progress)
* Deployment: Standardize on gunicorn, with gevent-based workers
and use of Green threads throughout Synnefo
* Documentation: New scale-out guide, with distinct node roles,
for mass Synnefo deployments
Astakos
-------
* Support multiple authentication methods
* Classic (username/password), Shibboleth, LDAP/Active Directory,
Google, Twitter, LinkedIn
* Users can enable/disable auth methods, and switch between them
* Introduce a UUID as a global identifier for users, throughout Synnefo
* The UUID remains constant as the user enables/disables login methods
* Allow users to modify their email address freely
* Per-user, per-resource accounting mechanism (quotaholder)
* Full quota support, with per-user, per-resource quotas, based on quotaholder
* Projects: Users can create and join Projects
* Projects grant extra resources to their members
* UI Enhancements for quotas and projects
* distinct Usage tab, showing usage of individual resources
* Project management UI
* New Overview page
Cyclades
--------
* Commission resources on quotaholder/Astakos
* Support mass creation of flavors
* Support for the ExtStorage disk template in Ganeti
* Query and report quotas in the UI
* Pass VM configuration parameters over a VM-side API (`vmapi`)
* Do not pass sensitive data as Ganeti OS parameters
* Keep sensitive data in memory caches (memcached) and
never allow them to hit the disk
* Display additional backend information in helpdesk machines list
* Allow helpdesk users to search for an account using a known machine id
* Helpdesk actions are now logged using the synnefo's common login
infrastructure
Pithos
------
* Support storage of blocks on a RADOS backend, for Archipelago
* new settings:
PITHOS_RADOS_STORAGE, PITHOS_RADOS_POOL_BLOCKS, PITHOS_RADOS_POOL_MAPS
* Rewritten support for public URLs, with admin-selectable length
* new settings:
PITHOS_PUBLIC_URL_SECURITY, PITHOS_PUBLIC_URL_ALPHABET
* Enable pithos backend to use external quotaholder component
* new settings:
PITHOS_USE_QUOTAHOLDER, PITHOS_QUOTAHOLDER_URL, PITHOS_QUOTAHOLDER_TOKEN,
PITHOS_QUOTAHOLDER_POOLSIZE
* Moderated version debiting mechanism
* new setting:
PITHOS_BACKEND_FREE_VERSIONING
* Proxy Astakos user-visible services
* new settings:
PITHOS_PROXY_USER_SERVICES, PITHOS_USER_CATALOG_URL,
PITHOS_USER_FEEDBACK_URL, PITHOS_USER_LOGIN_URL
Tools
-----
* Extend snf-burnin to include testing of Pithos functionality
.. _NEWS:
Unified NEWS file for Synnefo versions >= 0.13
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Since v0.13 all Synnefo components have been merged into a single repository.
.. _NEWS-0.13:
v0.13
=====
Release Date: UNRELEASED
Synnefo-wide
------------
* Support for pooling throughout Synnefo
* Pooled Django DB connections, Pithos backend connections, HTTP
connections using single `objpool` package
* Improved management commands
* Unified codebase for output of tables in JSON, CSV
* Bring most of Synnefo code inside a single, unified repository
* support automatic Python and Debian package builds for individual commits
* with automatic version generation
* Overhauling of Synnefo settings: renames and refactoring, for increased
uniformity (in progress)
* Deployment: Standardize on gunicorn, with gevent-based workers
and use of Green threads throughout Synnefo
* Documentation: New scale-out guide, with distinct node roles,
for mass Synnefo deployments
Astakos
-------
* Support multiple authentication methods
* Classic (username/password), Shibboleth, LDAP/Active Directory,
Google, Twitter, LinkedIn
* Users can enable/disable auth methods, and switch between them
* Introduce a UUID as a global identifier for users, throughout Synnefo
* The UUID remains constant as the user enables/disables login methods
* Allow users to modify their email address freely
* Per-user, per-resource accounting mechanism (quotaholder)
* Full quota support, with per-user, per-resource quotas, based on quotaholder
* Projects: Users can create and join Projects
* Projects grant extra resources to their members
* UI Enhancements for quotas and projects
* distinct Usage tab, showing usage of individual resources
* Project management UI
* New Overview page
Cyclades
--------
* Commission resources on quotaholder/Astakos
* Support mass creation of flavors
* Support for the ExtStorage disk template in Ganeti
* Query and report quotas in the UI
* Pass VM configuration parameters over a VM-side API (`vmapi`)
* Do not pass sensitive data as Ganeti OS parameters
* Keep sensitive data in memory caches (memcached) and
never allow them to hit the disk
* Display additional backend information in helpdesk machines list
* Allow helpdesk users to search for an account using a known machine id
* Helpdesk actions are now logged using the synnefo's common login
infrastructure
Pithos
------
* Support storage of blocks on a RADOS backend, for Archipelago
* Rewritten support for public URLs, with admin-selectable length
Tools
-----
* Extend snf-burnin to include testing of Pithos functionality
.. include:: ../Changelog
.. include:: ../NEWS
......@@ -180,6 +180,11 @@ in ``20-snf-astakos-app-settings.conf`` set::
# this will make the 'projects' page visible in the dashboard
ASTAKOS_PROJECTS_VISIBLE = True
You can specify a user-specific limit on pending project applications
with::
# snf-manage user-update <user id> --max-pending-projects=2
When users apply for projects they are not automatically granted
the resources. They must first be approved by the administrator.
......@@ -196,6 +201,12 @@ To deny an application::
# snf-manage project-control --deny <app id>
Users designated as *project admins* can approve, deny, or modify
an application through the web interface. In
``20-snf-astakos-app-settings.conf`` set::
# UUIDs of users that can approve or deny project applications from the web.
ASTAKOS_PROJECT_ADMINS = [<uuid>, ...]
Astakos advanced operations
......@@ -1221,21 +1232,16 @@ Node10:
All sections: :ref:`Scale out Guide <i-synnefo>`
Synnefo Upgrade Notes
=====================
Upgrade Notes
=============
.. toctree::
:maxdepth: 1
v0.12 -> v0.13 <upgrade/upgrade-0.13>
Older Cyclades Upgrade Notes
============================
.. toctree::
:maxdepth: 2
Upgrade <upgrade/cyclades-upgrade>
Changelog, NEWS
===============
Changelog
=========
* v0.13 :ref:`Changelog <Changelog-0.13>`, :ref:`NEWS <NEWS-0.13>`
......@@ -987,11 +987,11 @@ Pithos uses the alembic_ database migrations tool.
.. _alembic: http://alembic.readthedocs.org
After a sucessful installation, we should stamp it with the most recent
revision, in order to be able in the future to define the migrations should run
in subsequent upgrades.
After a sucessful installation, we should stamp it at the most recent
revision, so that future migrations know where to start upgrading in
the migration history.
In order to find the most recent revision, we check the migration history:
First, find the most recent revision in the migration history:
.. code-block:: console
......
include README Changelog
include README
include distribute_setup.py
global-include */templates/* */fixtures/* */static/*
global-exclude */.DS_Store
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment