cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9299) Out-of-band Management for CloudStack
Date Mon, 02 May 2016 18:17:13 GMT


ASF GitHub Bot commented on CLOUDSTACK-9299:

Github user jburwell commented on a diff in the pull request:
    --- Diff: api/src/org/apache/cloudstack/outofbandmanagement/
    @@ -0,0 +1,51 @@
    +// Licensed to the Apache Software Foundation (ASF) under one
    +// or more contributor license agreements.  See the NOTICE file
    +// distributed with this work for additional information
    +// regarding copyright ownership.  The ASF licenses this file
    +// to you 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
    +// Unless required by applicable law or agreed to in writing,
    +// software distributed under the License is distributed on an
    +// KIND, either express or implied.  See the License for the
    +// specific language governing permissions and limitations
    +// under the License.
    +package org.apache.cloudstack.outofbandmanagement;
    +import org.apache.cloudstack.api.response.OutOfBandManagementResponse;
    +import org.apache.cloudstack.framework.config.ConfigKey;
    +import java.util.List;
    +public interface OutOfBandManagementService {
    +    ConfigKey<Long> OutOfBandManagementActionTimeout = new ConfigKey<Long>("Advanced",
Long.class, "outofbandmanagement.action.timeout", "60",
    +                    "The out of band management action timeout in seconds, configurable
by cluster", true, ConfigKey.Scope.Cluster);
    +    ConfigKey<Long> OutOfBandManagementSyncThreadInterval = new ConfigKey<Long>("Advanced",
Long.class, "outofbandmanagement.sync.interval", "300000",
    +            "The interval (in milliseconds) when the out-of-band management background
sync are retrieved", true, ConfigKey.Scope.Global);
    +    ConfigKey<Integer> OutOfBandManagementSyncThreadPoolSize = new ConfigKey<Integer>("Advanced",
Integer.class, "outofbandmanagement.sync.poolsize", "50",
    +            "The out of band management background sync thread pool size", true, ConfigKey.Scope.Global);
    +    long getId();
    +    boolean isOutOfBandManagementEnabled(Host host);
    +    void submitBackgroundPowerSyncTask(Host host);
    +    boolean transitionPowerStateToDisabled(List<? extends Host> hosts);
    +    OutOfBandManagementResponse enableDisableOutOfBandManagement(DataCenter zone, boolean
    +    OutOfBandManagementResponse enableDisableOutOfBandManagement(Cluster cluster, boolean
    +    OutOfBandManagementResponse enableDisableOutOfBandManagement(Host host, boolean enabled);
    --- End diff --
    Why not name these methods either ``enableOutOfBandManagement`` or ``disableOutOfBandManagement``?
 The naming seems ambiguous as it does not indicate what a ``true`` or ``false`` value means
for the ``enabled`` parameter.

> Out-of-band Management for CloudStack
> -------------------------------------
>                 Key: CLOUDSTACK-9299
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.9.0, Future
> Support access to a host’s out-of-band management interface (e.g. IPMI, iLO, DRAC,
etc.) to manage host power operations (on/off etc.) and querying current power state.
> FS:

This message was sent by Atlassian JIRA

View raw message