This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Ganeti core".

The branch, master has been updated
       via  bf9f9a7c71071a79cf9bdabf5e186b2c773a5b06 (commit)
       via  b83fcc56d27af4280ed5e1a9c042905acc530cda (commit)
       via  f5bb63aebc1e9daadad9ce484867fcda52a77733 (commit)
       via  26ec766b398f160af37ed65a9eb639991740ba0a (commit)
       via  3d7ef7feee1e41efe5791f78c32af44312adf0c1 (commit)
       via  60554deab81b772a644e59cc89c2310db07a1e4d (commit)
       via  4f371ec96fa4086cda105594a0a693a4241afb25 (commit)
       via  b965855bd0ae26543aaab4a446ea75be4cb85458 (commit)
       via  f63bfd37950cae927e3ad32a2e9212335c54aa87 (commit)
       via  0f3e4b551214cb14093c4675b8b5dd10d66fb835 (commit)
       via  2c90ea7f1cfff2f8ce5a593210d2fd11261d8c1a (commit)
       via  0704f3f70728d28b6ad65ca912e0a5d764a6100f (commit)
       via  d4640c7a58d7513ebab7883f7cf077901b4e358f (commit)
       via  860627332e498c1d85ceba0f76e0eb842cff8fcc (commit)
       via  9cea1b5daf51149df4d6735b5b062889c4c02001 (commit)
       via  61a4f06d1e9515cf0610139ac9a40777e9241858 (commit)
      from  4462a8345b0ae41324a5b034841612af615c48c6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit bf9f9a7c71071a79cf9bdabf5e186b2c773a5b06
Author: Klaus Aehlig <[email protected]>
Date:   Wed Nov 19 11:25:52 2014 +0100

    Support removing forthcoming instances
    
    ...by restricting all physical operations to real
    objects, ignoring all operations that would have to
    be carried out on a forthcoming object. So, for the
    typical case (all forthcoming) it would mean only
    removing the entry from the configuration.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit b83fcc56d27af4280ed5e1a9c042905acc530cda
Author: Klaus Aehlig <[email protected]>
Date:   Wed Nov 19 11:51:26 2014 +0100

    Document --forthcoming in the man page
    
    ...stating that it can be used to only reserve the
    resources without creating the actual instance.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit f5bb63aebc1e9daadad9ce484867fcda52a77733
Author: Klaus Aehlig <[email protected]>
Date:   Mon Nov 17 19:35:47 2014 +0100

    Add --forthcoming to gnt-instance add
    
    ...and pass the flag through to LUInstanceCreate.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 26ec766b398f160af37ed65a9eb639991740ba0a
Author: Klaus Aehlig <[email protected]>
Date:   Mon Nov 17 20:43:24 2014 +0100

    Make GenericInstanceCreate honor forthcoming option
    
    ...and generate the opcode accordingly in this case.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 3d7ef7feee1e41efe5791f78c32af44312adf0c1
Author: Klaus Aehlig <[email protected]>
Date:   Mon Nov 17 19:26:44 2014 +0100

    Add a --forthcoming option
    
    This option will be used by gnt-instance add to allow creation of
    forthcoming instances.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 60554deab81b772a644e59cc89c2310db07a1e4d
Author: Klaus Aehlig <[email protected]>
Date:   Tue Nov 18 12:59:26 2014 +0100

    Support forthcoming in LUIntanceCreate
    
    If a forthcoming instance is requested, we just reserve the resources,
    but don't create the instance itself.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 4f371ec96fa4086cda105594a0a693a4241afb25
Author: Klaus Aehlig <[email protected]>
Date:   Tue Nov 18 13:10:16 2014 +0100

    Support forthcoming in generating disk templates
    
    ...by just passing through that bit to the disk objects.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit b965855bd0ae26543aaab4a446ea75be4cb85458
Author: Klaus Aehlig <[email protected]>
Date:   Tue Nov 18 11:47:06 2014 +0100

    Add pForthcoming to OpInstanceCreate
    
    ...allowing to specify that the instance is to be
    created as forthcoming, i.e., only resources to
    be reserved.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit f63bfd37950cae927e3ad32a2e9212335c54aa87
Author: Klaus Aehlig <[email protected]>
Date:   Tue Nov 18 11:42:52 2014 +0100

    Add an OpParam for forthcoming objects
    
    We will add this parameter to opcodes creating objects
    that might have a forthcoming variant. If present and
    set to true, create the object as forthcoming, i.e.,
    only reserve the resources.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 0f3e4b551214cb14093c4675b8b5dd10d66fb835
Author: Klaus Aehlig <[email protected]>
Date:   Tue Nov 18 19:48:00 2014 +0100

    For an instance report only the real LVs
    
    When getting the logical volumes an instance owns (grouped
    by node) only report the non-forthcoming ones. Only those
    will be observable on the node.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 2c90ea7f1cfff2f8ce5a593210d2fd11261d8c1a
Author: Klaus Aehlig <[email protected]>
Date:   Mon Nov 17 11:38:21 2014 +0100

    Make handling of forthcoming instances opt-in
    
    Change all logical units to reject handling forthcoming
    instances. We will later, one by one, add support for
    forthcoming instances as needed. As most logical units
    handling instances start with _ExpandAndLockInstance, we
    have a central place to set the default.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 0704f3f70728d28b6ad65ca912e0a5d764a6100f
Author: Klaus Aehlig <[email protected]>
Date:   Fri Nov 14 12:51:24 2014 +0100

    Remove forthcoming disks on downgrade
    
    Forthcoming disks were newly introduced in Ganeti 2.14, hence
    remove them on downgrade. Also remove them from the disks entry
    of all (not forthcoming, and hence not removed anyway) instances.
    Note that nothing has to be changed in the physical world, as
    forthcoming disks are not yet created.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit d4640c7a58d7513ebab7883f7cf077901b4e358f
Author: Klaus Aehlig <[email protected]>
Date:   Fri Nov 14 10:35:16 2014 +0100

    Remove forthcoming instances on downgrade
    
    Forthcoming instances were newly introduced in Ganeti 2.14, hence
    remove them on downgrade. Note that nothing has to be changed in
    the physical world, as forthcoming instances are not created yet.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 860627332e498c1d85ceba0f76e0eb842cff8fcc
Author: Klaus Aehlig <[email protected]>
Date:   Fri Nov 14 09:48:47 2014 +0100

    Allow instances to be forthcoming
    
    ...by adding an appropriate slot to the instance objects.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 9cea1b5daf51149df4d6735b5b062889c4c02001
Author: Klaus Aehlig <[email protected]>
Date:   Thu Nov 13 17:43:33 2014 +0100

    Allow forthcoming Disks
    
    ...by adding a "forthcoming" slot to the disk objects.
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

commit 61a4f06d1e9515cf0610139ac9a40777e9241858
Author: Klaus Aehlig <[email protected]>
Date:   Wed Nov 19 11:19:45 2014 +0100

    Move assertions to beginning of ExecBlock
    
    Usually we aim for operations to succeed or not do
    anything at all. Do the same when failing for internal
    errors (like bugs in the locks requesting code).
    
    Signed-off-by: Klaus Aehlig <[email protected]>
    Reviewed-by: Niklas Hambuechen <[email protected]>

-----------------------------------------------------------------------

Summary of changes:
 lib/cli.py                     |    5 +++++
 lib/cli_opts.py                |    6 ++++++
 lib/client/gnt_instance.py     |    1 +
 lib/cmdlib/base.py             |   10 +++++++++-
 lib/cmdlib/instance.py         |   35 ++++++++++++++++++++---------------
 lib/cmdlib/instance_create.py  |   10 +++++++++-
 lib/cmdlib/instance_storage.py |   17 ++++++++++-------
 lib/config/__init__.py         |    3 ++-
 lib/objects.py                 |    2 ++
 man/gnt-instance.rst           |    6 +++++-
 src/Ganeti/OpCodes.hs          |    1 +
 src/Ganeti/OpParams.hs         |    6 ++++++
 test/hs/Test/Ganeti/OpCodes.hs |    1 +
 tools/cfgupgrade               |   28 ++++++++++++++++++++++++++++
 14 files changed, 105 insertions(+), 26 deletions(-)


hooks/post-receive
-- 
Ganeti core

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ganeti-commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to