blob: aea016517a50d7aaf2ec25f62fd1b5735886e588 [file] [log] [blame]
// 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
//
// 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.
#ifndef __WINDOWS_FILESYSTEM_ISOLATOR_HPP__
#define __WINDOWS_FILESYSTEM_ISOLATOR_HPP__
#include <mesos/resources.hpp>
#include "slave/flags.hpp"
#include "slave/containerizer/mesos/isolator.hpp"
#include "slave/containerizer/mesos/isolators/filesystem/posix.hpp"
#include "slave/volume_gid_manager/volume_gid_manager.hpp"
namespace mesos {
namespace internal {
namespace slave {
// TODO(hausdorff): (MESOS-5462) For now the Windows isolators are essentially
// direct copies of their POSIX counterparts. In the future, we expect to
// refactor the POSIX classes into platform-independent base class, with
// Windows and POSIX implementations. For now, we leave the Windows
// implementations as inheriting from the POSIX implementations.
class WindowsFilesystemIsolatorProcess : public PosixFilesystemIsolatorProcess
{
public:
static Try<mesos::slave::Isolator*> create(
const Flags& flags,
VolumeGidManager* volumeGidManager);
private:
WindowsFilesystemIsolatorProcess(
const Flags& flags,
VolumeGidManager* volumeGidManager);
};
} // namespace slave {
} // namespace internal {
} // namespace mesos {
#endif // __WINDOWS_FILESYSTEM_ISOLATOR_HPP__