Canberra's Afterlife. Highpressure Crystals and the Bush Capital Dream

Canberra, the ?Bush Capital? of Australia, was a project torn between ambition and avoidance. For fear of upsetting Sydney or Melbourne, its location avoided larger territorial aspirations but its crystalline winning scheme was bold, and contained the promise of enlightened irradiation. Postwar Canberra, like so many other cities at the time, let its future be designed by Cold-War traffic engineers, who confidently turned dream into sprawl and highways. Although Canberra s mix of ambition and banality, of symbolic desire and structural normalcy, may be precisely what a good city is all about, it probably contains these in defective proportions. What Canberra needs is just a little more of itself, in different amounts, to a higher pressure from the inside. We can easily imagine the multiplying of the original Griffin plan, adding the city onto itself, organizing the recent sprawl with new nodes and public transport with more urban streets between them. With this reclaimed space for higher density, Canberra can then grow from the inside instead of sprawling away, lowering its expenditure on transport and its carbon and sustainability footprint. The new nodes will be denser and allow for variety and change in its programmatic design. Minor but detailed changes in street and public space design will also allow for easier multi-species (people, animals?) access to urban and natural resources. Video brief of the project: http://vimeo.com/45799435

Entre: de repente, sin fin, lo innombrable

Etiquetamos para reducir nuestra incertidumbre; clasificamos en base a términos opuestos para poder entender. El universo y el espacio construido en particular, se explican desde una arquitectónica dual: dentro – fuera, arriba – abajo, derecha – izquierda, día – noche, hombre – mujer. Lo que nos diferencia como grupo, raza o género, distinguiendo los modos de vivir, las ideologías y las teorías, es la relación que establecemos entre los términos opuestos: entre lo individual y lo colectivo, lo privado y lo público, la imaginación y la realidad, la identidad y la otredad, el orden y el caos, el deseo y la saciedad. El afán clasificatorio dicotómico de la realidad que la modernidad lleva a su extremo, hiere la vida: la mutua exclusión de los opuestos elimina la distancia, el espacio-tiempo entre ambos, que es donde la vida se sitúa. La concepción dual que rige nuestro conocimiento contamina también la relación entre los arquitectos y la sociedad, siendo la causa del ambiente tóxico que envuelve al habitante que ya no se identifica con los lugares que habita. Puede que sea oportuno pasar del pensamiento binario a una lógica de lo intersticial que abandone la dualidad para instalarse en el Entre; los arquitectos serían mediadores entre el poder y la vida, sintiendo el Entre como el transcurso de la vida y la potencia de interacción: los lugares ambiguos e intermedios, es donde sucede el encuentro entre los términos, entre arquitectos y habitantes, entre la imaginación y la realidad, entre tú y yo. ABSTRACT We label to reduce our uncertainty; we classify based on opposites to understand. The universe and all constructed space in particular, are explained from a dual architecture: inside - out, up - down, right - left, day - night, male - female, black - white. What differentiate us as a group, race, gender, distinguishing the lifestyles, ideologies and theories, is how we draw the relation between the opposites: between the individual and the collective, private and public, imagination and reality , identity and otherness, order and disorder, desire and satiety. The dichotomous classification of reality that modernity carried to its extreme, hurts life: the mutual exclusion of opposites eliminates the distance, the space-time between the two, which is where life is located. The dual conception that governs our knowledge has also contaminated the relationship between architect and society, being the cause of the toxic environment that surrounds the inhabitant who no longer identify himself with the places he inhabit. It may be appropriate pass from binary thinking to a logic of the interstitial which abandon duality to settle in Between; architect then will be the mediator between authorities and life, sensing the Between as a flowing of life a potency of interaction rather than a separation between the extremes; ambiguous, in –between, places are where the encounter between opposites happens, between the architect and the inhabitant, between imagination and reality, between you and me.

Infrastructure (Resilience-oriented) Modelling Language: I®ML A proposal for modelling infrastructures and their connections

The modelling of critical infrastructures (CIs) is an important issue that needs to be properly addressed, for several reasons. It is a basic support for making decisions about operation and risk reduction. It might help in understanding high-level states at the system-of-systems layer, which are not ready evident to the organisations that manage the lower level technical systems. Moreover, it is also indispensable for setting a common reference between operator and authorities, for agreeing on the incident scenarios that might affect those infrastructures. So far, critical infrastructures have been modelled ad-hoc, on the basis of knowledge and practice derived from less complex systems. As there is no theoretical framework, most of these efforts proceed without clear guides and goals and using informally defined schemas based mostly on boxes and arrows. Different CIs (electricity grid, telecommunications networks, emergency support, etc) have been modelled using particular schemas that were not directly translatable from one CI to another. If there is a desire to build a science of CIs it is because there are some observable commonalities that different CIs share. Up until now, however, those commonalities were not adequately compiled or categorized, so building models of CIs that are rooted on such commonalities was not possible. This report explores the issue of which elements underlie every CI and how those elements can be used to develop a modelling language that will enable CI modelling and, subsequently, analysis of CI interactions, with a special focus on resilience

A proposal for a modular and application-aware autonomic manager of private cloud infrastructures

Recientemente, el paradigma de la computación en la nube ha recibido mucho interés por parte tanto de la industria como del mundo académico. Las infraestructuras cloud públicas están posibilitando nuevos modelos de negocio y ayudando a reducir costes. Sin embargo, una compañía podría desear ubicar sus datos y servicios en sus propias instalaciones, o tener que atenerse a leyes de protección de datos. Estas circunstancias hacen a las infraestructuras cloud privadas ciertamente deseables, ya sea para complementar a las públicas o para sustituirlas por completo. Por desgracia, las carencias en materia de estándares han impedido que las soluciones para la gestión de infraestructuras privadas se hayan desarrollado adecuadamente. Además, la multitud de opciones disponibles ha creado en los clientes el miedo a depender de una tecnología concreta (technology lock-in). Una de las causas de este problema es la falta de alineación entre la investigación académica y los productos comerciales, ya que aquella está centrada en el estudio de escenarios idealizados sin correspondencia con el mundo real, mientras que éstos consisten en soluciones desarrolladas sin tener en cuenta cómo van a encajar con los estándares más comunes o sin preocuparse de hacer públicos sus resultados. Con objeto de resolver este problema, propongo un sistema de gestión modular para infraestructuras cloud privadas enfocado en tratar con las aplicaciones en lugar de centrarse únicamente en los recursos hardware. Este sistema de gestión sigue el paradigma de la computación autónoma y está diseñado en torno a un modelo de información sencillo, desarrollado para ser compatible con los estándares más comunes. Este modelo divide el entorno en dos vistas, que sirven para separar aquello que debe preocupar a cada actor involucrado del resto de información, pero al mismo tiempo permitiendo relacionar el entorno físico con las máquinas virtuales que se despliegan encima de él. En dicho modelo, las aplicaciones cloud están divididas en tres tipos genéricos (Servicios, Trabajos de Big Data y Reservas de Instancias), para que así el sistema de gestión pueda sacar partido de las características propias de cada tipo. El modelo de información está complementado por un conjunto de acciones de gestión atómicas, reversibles e independientes, que determinan las operaciones que se pueden llevar a cabo sobre el entorno y que es usado para hacer posible la escalabilidad en el entorno. También describo un motor de gestión encargado de, a partir del estado del entorno y usando el ya mencionado conjunto de acciones, la colocación de recursos. Está dividido en dos niveles: la capa de Gestores de Aplicación, encargada de tratar sólo con las aplicaciones; y la capa del Gestor de Infraestructura, responsable de los recursos físicos. Dicho motor de gestión obedece un ciclo de vida con dos fases, para así modelar mejor el comportamiento de una infraestructura real. El problema de la colocación de recursos es atacado durante una de las fases (la de consolidación) por un resolutor de programación entera, y durante la otra (la online) por un heurístico hecho ex-profeso. Varias pruebas han demostrado que este acercamiento combinado es superior a otras estrategias. Para terminar, el sistema de gestión está acoplado a arquitecturas de monitorización y de actuadores. Aquella estando encargada de recolectar información del entorno, y ésta siendo modular en su diseño y capaz de conectarse con varias tecnologías y ofrecer varios modos de acceso. ABSTRACT The cloud computing paradigm has raised in popularity within the industry and the academia. Public cloud infrastructures are enabling new business models and helping to reduce costs. However, the desire to host company’s data and services on premises, and the need to abide to data protection laws, make private cloud infrastructures desirable, either to complement or even fully substitute public oferings. Unfortunately, a lack of standardization has precluded private infrastructure management solutions to be developed to a certain level, and a myriad of diferent options have induced the fear of lock-in in customers. One of the causes of this problem is the misalignment between academic research and industry ofering, with the former focusing in studying idealized scenarios dissimilar from real-world situations, and the latter developing solutions without taking care about how they f t with common standards, or even not disseminating their results. With the aim to solve this problem I propose a modular management system for private cloud infrastructures that is focused on the applications instead of just the hardware resources. This management system follows the autonomic system paradigm, and is designed around a simple information model developed to be compatible with common standards. This model splits the environment in two views that serve to separate the concerns of the stakeholders while at the same time enabling the traceability between the physical environment and the virtual machines deployed onto it. In it, cloud applications are classifed in three broad types (Services, Big Data Jobs and Instance Reservations), in order for the management system to take advantage of each type’s features. The information model is paired with a set of atomic, reversible and independent management actions which determine the operations that can be performed over the environment and is used to realize the cloud environment’s scalability. From the environment’s state and using the aforementioned set of actions, I also describe a management engine tasked with the resource placement. It is divided in two tiers: the Application Managers layer, concerned just with applications; and the Infrastructure Manager layer, responsible of the actual physical resources. This management engine follows a lifecycle with two phases, to better model the behavior of a real infrastructure. The placement problem is tackled during one phase (consolidation) by using an integer programming solver, and during the other (online) with a custom heuristic. Tests have demonstrated that this combined approach is superior to other strategies. Finally, the management system is paired with monitoring and actuators architectures. The former able to collect the necessary information from the environment, and the later modular in design and capable of interfacing with several technologies and ofering several access interfaces.